Hi!
(I hope this doesn't go through in triplicate, but I originally tried
posting via the newsgroup that linux-gate was mirroring for this
mailinglist, but it or google gruops seems to be
eating my messages, no idea why)
I recently reinstalled my (outdated) Debian Unstable to Debian Testing.
When this was completed, I attempted mounting the datapartitions from
my old installation, and I had a bit of problems.
Basically, I have a software raid (raid1, mirror) /dev/md0, on top of
it I have a lvm, and that lvm is set up to two differentl logical
volumes; "encrypted" and "plain".
"encrypted" is a blockdevice for cryptsetup, and after I reinstalled it
seemed as though I've got the wrong passphrase (could just as well be
true, because I haven't entered the unique password for 330 days) -
this in itself wasn't that alarming. The real issue was with "plain" -
which is a simple ext3-partition. When I mounted it, I first got a bit
of garbage in my ls -l output. I.e. uid and gid was shown as "?"
(iirc), and the permissions were nonsensical. Still, it gave me a
listing of the dirs and files on it. I just left it for later, it being
the middle of christmas. Now, it shows it as empty (only "lost+found"
still onit), dmesg has some peculiar output and fsck gives a *lot* of
errors regarding i_blocks (see below). This could be some kind of
hardware malfunction, but I *am* running raid1 which should prevent
that, and it seems peculiar that it occured at the same time as I
reinstalled my system (no physical activity that could cause any direct
damage). And to mention it, I went from kernel 2.6.8 to 2.6.18-3. :-)
Any suggestions would *really* be appreciated. :-)
This is the relevant data from my system (mdadm info, lvm info, dmesg
errors and fsck errors):
mental:~# mdadm --misc --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Thu Jul 21 21:38:43 2005
Raid Level : raid1
Array Size : 78150656 (74.53 GiB 80.03 GB)
Device Size : 78150656 (74.53 GiB 80.03 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Jan 7 17:49:09 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 10303d9e:896dc2b5:091fe5d8:4ca9cbd4
Events : 0.4592
Number Major Minor RaidDevice State
0 3 64 0 active sync /dev/hdb
1 22 64 1 active sync /dev/hdd
mental:~# lvdisplay; vgdisplay; pvdisplay
--- Logical volume ---
LV Name /dev/raid/encrypted
VG Name raid
LV UUID qUoaKV-bA2d-hMZT-4J1w-dQcY-XnDD-ve2EEt
LV Write Access read/write
LV Status available
# open 1
LV Size 37,27 GB
Current LE 9540
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 254:0
--- Logical volume ---
LV Name /dev/raid/plain
VG Name raid
LV UUID pOicCC-nsci-2FPf-o4Z4-umBg-924j-qYys50
LV Write Access read/write
LV Status available
# open 0
LV Size 37,26 GB
Current LE 9539
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 254:1
--- Volume group ---
VG Name raid
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 74,53 GB
PE Size 4,00 MB
Total PE 19079
Alloc PE / Size 19079 / 74,53 GB
Free PE / Size 0 / 0
VG UUID gMj9Eo-u6UH-PFic-LlUl-gkSh-1To5-q1TD3N
--- Physical volume ---
PV Name /dev/md0
VG Name raid
PV Size 74,53 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 19079
Free PE 0
Allocated PE 19079
PV UUID bLiABd-5HT8-jCLG-PMn7-3UFf-0LLa-s75jwP
mental:~# dmesg|egrep 'EXT3-fs (error|warning)'
EXT3-fs warning: checktime reached, running e2fsck is recommended
EXT3-fs error (device dm-1): ext3_readdir: bad entry in directory
#4202749: rec_len is smaller than minimal - offset=0, inode=0,
rec_len=0, name_len=0
EXT3-fs error (device dm-1): ext3_journal_start_sb: Detected aborted
journal
EXT3-fs error (device dm-1): ext3_readdir: bad entry in directory
#3810221: rec_len is smaller than minimal - offset=0, inode=0,
rec_len=0, name_len=0
EXT3-fs warning (device dm-1): ext3_clear_journal_err: Filesystem error
recorded from previous mount: IO failure
EXT3-fs warning (device dm-1): ext3_clear_journal_err: Marking fs in
need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
mental:/mnt/oldroot# fsck -n /dev/mapper/raid-plain > output.log
e2fsck 1.40-WIP (14-Nov-2006)
e2fsck: aborted
output.log is 96kb, most of it goes like this:
Inode 555975, i_blocks is 316016, should be 8304. Fix? no
Inode 555970, i_blocks is 18488, should be 8320. Fix? no
Inode 555971, i_blocks is 23648, should be 8304. Fix? no
Inode 555972, i_blocks is 32264, should be 8304. Fix? no
Inode 555973, i_blocks is 13104, should be 8304. Fix? no
Inode 555974, i_blocks is 42616, should be 8304. Fix? no
Inode 556018, i_blocks is 1080, should be 104. Fix? no
Also some of it is like this:
mental:/mnt/oldroot# grep -v 'i_blocks is' output.log |grep Entry
Entry 'torrent' in / (2) has deleted/unused inode 1847777. Clear? no
Entry 'torrent' in / (2) has an incorrect filetype (was 2, should be
0).
Entry 'daxxar' in / (2) has deleted/unused inode 670433. Clear? no
Entry '..' in ??? (752193) has deleted/unused inode 670433. Clear? no
Entry 'manga' in ??? (752193) has deleted/unused inode 883009. Clear?
no
Entry '1_wildcard.swf' in ??? (752193) has deleted/unused inode
4169761. Clear? no
Entry '1_wildcard.swf' in ??? (752193) has an incorrect filetype (was
1, should be 0).
Entry 'zigzag' in ??? (752193) has deleted/unused inode 2812929.
Clear? no
Entry 'zigzag' in ??? (752193) has an incorrect filetype (was 2, should
be 0).
Entry 'files' in ??? (752193) has deleted/unused inode 703585. Clear? no
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
