Hi all,
I fear that this will end in tears.
My home partition on a Debian wheezy install is an encrypted LVM volume. It
is ext3. Earlier today, I had a weird message in a terminal window about an
attempt to write to a file in my /home tree failing due to having a read
only file system. On reboot, I end up with an error message.
/dev/sda1 is reported as clean. fsck.ext3, which runs automatically reports
that there is no such device as /dev/mapper/sda1_crypt and reports exit
code 8. It drops me to a maintenance shell and tells me it tried to write
a log to /var/log/fsck/checkfs.
That log reads:
[Timestamp]
fsck from util-linux 2.20.1
/dev/mapper/sda1_crypt: Super blocks need_recovery flag is clear, but
journal has data.
/dev/mapper/sda1_crypt: Run journal anyway
/dev/mapper/sda1_crypt: IN EXPECT D INCONSISTENCY; RUN fsck MANUALLY
(i.e., without -a or -p options)
fsck died with exit status 4
I ran
$ fsck -vnM /dev/mapper/sda1
A bunch of illegal block #nnnn (mmmmmmmmm) in inode ppppppp IGNORED
messages followed by
too many blocks in Inode pppppppp
Then running additional passes to resolve blocks claimed by more than one
inode
Pass 1B: Rescanning for multiply claimed blocks
I got a wall of
Illegal block number passed to ext2fs_test_block_bitmap #nnnnnnnnn for
multiply claimed block map
lines.
These were followed by 2 Multiply claimed blocks in I node nnnnnnnnn:
[lists of 5 and 8 block numbers]
Then I got a number of stanzas like
[ 3828.181915] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3828.182462] ata1.01 BMDMA stat 0x64
[ 3828.183810] ata1.01 failed command: READ DMA EXT
[ 3828.185889] ata1.01 cmd 25/00:08:08:10:9c/00:00:29:00:00/f0 tag dma 4096
in
[ 3828.185891] res 51/40:00:09:10:9c/40:00:29:00:00/f0 Emask 0x9 (media
error)
[ 3828.190071] ata1.01 status: { DRDY ERR }
[ 3828.192153] ata1.01 status: { UNC }
These were followed by
[ 3830.509338] end_request: I/O error, deb SDA, sector 698093577
[ 3830.509841] Buffer I/O error on device dm-3, logical block 87261184
Error reading block 87261184 (Attempt to read block from filesystem
resulted in short read) while reading I node and block bitmaps. Ignore
error? no
fsck.ext3: Can't read an block bitmap while retrying to read bitmaps for
/dev/mappersfa1_crypt
/dev/mapper/sda1_crypt: ******* WARNING: Filesystem still has errors *******
e2fsck: aborted
/dev/mapper/sda1_crypt: ******* WARNING: Filesystem still has errors *******
And the it aborted with a warning that the filesystem still had errors.
My questions are:
1) Is my data toasted? (My rigorous backup policy hasn't been rigorously
followed of late; I am being punished by the universe, I am sure.)
2) What can/ought I to do now?
3) Did I do the wrong thing already?
4) Will someone hold me until the shaking stops?
Thanks and best,
Brian vdB
_______________________________________________
mlug mailing list
[email protected]
https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
