Re: Revert Fix-EXT_MAX_BLOCK.patch

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

 



On Thu, Jul 10, 2008 at 06:08:03PM +0530, Aneesh Kumar K.V wrote:
> On Thu, Jul 10, 2008 at 08:22:42AM -0400, Theodore Tso wrote:
> > Aneesh, for the record, how were you able to reproduce the problem?
> > 
> > Do you have Holger's afdbench setup, or did you use some other workload?
> > 
> 
> cp -ax /usr . 
> 
> that will cause the BUG

Hmm, I wasn't able to trigger it so easily, at least, while trying to
replicate Gary Hawco's, bug.  (Which also had Fix-EXT_MAX_BLOCK
applied.)  I wonder if he wasn't able to trigger it while doing the
partial rollback, and so ext4-fix-mb_find_next_bit-return.patch was
unfairly blamed for the BUG.

In any case, both patches have been pulled out of the patch series ,
and I'll release a new patchset until we can figure out what happened.

(Gary, this is why its important to get the kernel BUG/oops message;
it helps us correlate your bug reports with others.)

						- Ted
--
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