** Description changed:

- Binary package hint: linux-image-2.6.20-15-generic
+ Kernel crashes in ext3 dx_probe. "BUG at fs/ext3/namei.c:384! "
  
+ This bug has been reported with linux-image-2.6.20-15-generic (this bug
+ #109177 and bug #122116) and with linux-image-2.6.20-16-generic (bug
+ #120179). Bug #106830 misinterpreted this as a bug in "pan" -- but it is
+ actually a kernel bug in handling a corrupt ext3 fs.
  
- 
- Note: bug #106830 misinterpreted this as a bug in "pan" -- but it is actually 
a kernel bug in handling a corrupt ext3 fs.
+ Reading a corrupt filesystem might trigger this bug (bug #122116). Could
+ this be somehow related to ext3 filesystem corruption, bugs #65815 Ext3
+ corruption on a drive), #53102 ext3 partitions are getting corrupt more
+ often than they should, bug #66032 fsck.ext3: Unable to resolve, bug
+ #118256 ext3 data corruption with kernel 2.6.20-16-generic?

** Tags added: corruption ext3

** Description changed:

  Kernel crashes in ext3 dx_probe. "BUG at fs/ext3/namei.c:384! "
  
  This bug has been reported with linux-image-2.6.20-15-generic (this bug
  #109177 and bug #122116) and with linux-image-2.6.20-16-generic (bug
  #120179). Bug #106830 misinterpreted this as a bug in "pan" -- but it is
  actually a kernel bug in handling a corrupt ext3 fs.
  
  Reading a corrupt filesystem might trigger this bug (bug #122116). Could
- this be somehow related to ext3 filesystem corruption, bugs #65815 Ext3
- corruption on a drive), #53102 ext3 partitions are getting corrupt more
- often than they should, bug #66032 fsck.ext3: Unable to resolve, bug
- #118256 ext3 data corruption with kernel 2.6.20-16-generic?
+ this be somehow related to ext3 filesystem corruption, bug #65815 Ext3
+ corruption on a drive), bug #53102 ext3 partitions are getting corrupt
+ more often than they should, bug #66032 fsck.ext3: Unable to resolve,
+ bug #118256 ext3 data corruption with kernel 2.6.20-16-generic?

-- 
[Feisty] Kernel crashes in ext3 dx_probe
https://bugs.launchpad.net/bugs/109177
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to