Public bug reported:
I have a forensic image of a file system:
# file dev_sda2.dd
dev_sda2.dd: Linux rev 1.0 ext3 filesystem data (needs journal recovery)
Under 2.6.27-9 (x86_64) it was possible to mount this image read-only
using an alternate superblock like so:
# mount -o ro,loop,sb=131072 dev_sda2.dd /mnt
Again with 2.6.27-9 (x86_64) dmesg would show:
[ 411.272510] JBD: Ignoring recovery information on journal
[ 411.296336] __ratelimit: 51 callbacks suppressed
[ 411.296350] Buffer I/O error on device loop0, logical block 0
[ 411.296357] lost page write due to I/O error on loop0
[ 411.296368] Buffer I/O error on device loop0, logical block 1
[ 411.296373] lost page write due to I/O error on loop0
[ 411.296381] Buffer I/O error on device loop0, logical block 2
[ 411.296385] lost page write due to I/O error on loop0
[ 411.296393] Buffer I/O error on device loop0, logical block 3
[ 411.296398] lost page write due to I/O error on loop0
[ 411.296407] Buffer I/O error on device loop0, logical block 18
[ 411.296411] lost page write due to I/O error on loop0
[ 411.296419] Buffer I/O error on device loop0, logical block 32
[ 411.296424] lost page write due to I/O error on loop0
[ 411.296432] Buffer I/O error on device loop0, logical block 73
[ 411.296436] lost page write due to I/O error on loop0
[ 411.296444] Buffer I/O error on device loop0, logical block 74
[ 411.296448] lost page write due to I/O error on loop0
[ 411.296456] Buffer I/O error on device loop0, logical block 94
[ 411.296461] lost page write due to I/O error on loop0
[ 411.296468] Buffer I/O error on device loop0, logical block 96
[ 411.296473] lost page write due to I/O error on loop0
[ 411.296800] kjournald starting. Commit interval 5 seconds
[ 411.296836] EXT3-fs: mounted filesystem with ordered data mode.
After upgrading to 2.6.27-11 (x86_64) the same mount command fails:
# mount -o ro,loop,sb=131072 dev_sda2.dd /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Under 2.6.27-11 (x86_64) dmesg shows:
[ 492.680682] JBD: Ignoring recovery information on journal
[ 492.917334] Buffer I/O error on device loop0, logical block 0
[ 492.917347] lost page write due to I/O error on loop0
[ 492.917353] Buffer I/O error on device loop0, logical block 1
[ 492.917355] lost page write due to I/O error on loop0
[ 492.917359] Buffer I/O error on device loop0, logical block 2
[ 492.917361] lost page write due to I/O error on loop0
[ 492.917364] Buffer I/O error on device loop0, logical block 3
[ 492.917366] lost page write due to I/O error on loop0
[ 492.917370] Buffer I/O error on device loop0, logical block 18
[ 492.917372] lost page write due to I/O error on loop0
[ 492.917376] Buffer I/O error on device loop0, logical block 32
[ 492.917378] lost page write due to I/O error on loop0
[ 492.917382] Buffer I/O error on device loop0, logical block 73
[ 492.917384] lost page write due to I/O error on loop0
[ 492.917387] Buffer I/O error on device loop0, logical block 74
[ 492.917389] lost page write due to I/O error on loop0
[ 492.917393] Buffer I/O error on device loop0, logical block 94
[ 492.917395] lost page write due to I/O error on loop0
[ 492.917399] Buffer I/O error on device loop0, logical block 96
[ 492.917401] lost page write due to I/O error on loop0
[ 492.917500] JBD: recovery failed
[ 492.917502] EXT3-fs: error loading journal.
I can provide the image file on request, but it's about 1GB in size...
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
Package: linux-image-2.6.27-11-generic 2.6.27-11.27
ProcCmdLine: root=/dev/mapper/hostname-root ro quiet splash
ProcEnviron:
PATH=/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/username/bin
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-11.27-generic
SourcePackage: linux
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug
--
regression in ext3 driver?
https://bugs.launchpad.net/bugs/326448
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
