On Thu, Mar 16, 2006 at 08:24:53AM +0100, Joel Soete wrote: > Hello all, > > here is a small report on some ext3 pb I encounter with vserver patch (at > least I didn't yet emcounter it without this patch but I didn't exclude arch > specific pb): > EXT3-fs error (device md2): ext3_readdir: bad entry in directory #16959: > rec_len % 4 != 0 - offset=0, inode=1947074816, rec_len=26638, name_len=16 > > Aborting journal on device md2. > > ext3_abort called. > > EXT3-fs error (device md2): ext3_journal_start_sb: Detected aborted journal > > Remounting filesystem read-only > > EXT3-fs error (device md2): ext3_readdir: bad entry in directory #16959: > rec_len % 4 != 0 - offset=0, inode=1947074816, rec_len=26638, name_len=16 > > (this mount point is simply the 'root' of a chrooted install) > > Fwiw, the mentioned dir is actualy: > find . -type d -inum 16959 > ./usr/share/doc/texmf/fontinst/talks > > but the inode 1947074816 is very unrelevant: > # ls -al ./usr/share/doc/texmf/fontinst/talks > total 0 > > (even if I search it over all the fs) > > The kernel is: > # uname -a > Linux patst007 2.6.16-rc5-vs2.1.1-rc12-pa2-d32up #4 Mon Mar 13 13:43:14 CET > 2006 parisc GNU/Linux > > Any idea?
it basically says that an entry in that directory does not fulfill some assertion (26638 % 4 = 2 != 0) I don't see how this would be linux-vserver related, but if you try with 2.6.16-rc5 vanilla, it doesn't happen? what does e2fsck say to that? HTH, Herbert > TIA, > Joel > > > > --------------------------------------------------------------- > A free anti-spam and anti-virus filter on all Scarlet mailboxes > More info on http://www.scarlet.be/ > > _______________________________________________ > Vserver mailing list > [email protected] > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
