Re: [Fwd: [Bug] 2.6.30 kernel stack trace with 'fsfuzzer ext3' on s390]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jun 29, 2009 at 02:42:43PM +0530, Nageswara R Sastry wrote:
> Hitting the same bug with 2.6.31-rc1 on s390 arch.
>
>
> EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in  
> directory #2: rec_len % 4 != 0 - offset=44, inode=12, rec_len=139,  
> name_len=10
> __log_wait_for_space: needed 256 blocks and only had 0 space available
> __log_wait_for_space: no way to get more journal space

Does this _only_ happen on s390? I would expect that this is not
architecture specific. Whatever fsfuzzer is doing.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux