Yo Yo, I can double confirm this. I am running a Dell Vostro 1500 I did a install of 7.10 server to get LVM. Created all my partitions and formatted them with reiserfs - no special options. I only copied over my home forlder from my old laptop.
Once I had the server install done, I did a "apt-get install ubuntu-desktop" During this I had bounced the laptop a couple of times - no problem. I then went to Hardy - which release I don't know - and bounced the laptop a couple of times fine. Then after another bounce I got the the following error Mar 10 12:05:03 opium kernel: [ 869.025959] ReiserFS: dm-2: found reiserfs format "3.6" with standard journal Mar 10 12:05:03 opium kernel: [ 869.025994] ReiserFS: dm-2: using ordered data mode Mar 10 12:05:03 opium kernel: [ 869.035345] ReiserFS: dm-2: journal params: device dm-2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Mar 10 12:05:03 opium kernel: [ 869.035820] ReiserFS: dm-2: checking transaction log (dm-2) Mar 10 12:05:03 opium kernel: [ 869.041754] ReiserFS: dm-2: warning: journal-2018: Bad transaction length 1936093797 encountered, ignoring transaction Mar 10 12:05:03 opium kernel: [ 869.066663] ReiserFS: warning: is_tree_node: node level 26691 does not match to the expected one 1 Mar 10 12:05:03 opium kernel: [ 869.066677] ReiserFS: dm-2: warning: vs-5150: search_by_key: invalid format found in block 8211. Fsck? Mar 10 12:05:03 opium kernel: [ 869.066689] ReiserFS: dm-2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1 2 0x0 SD] Mar 10 12:05:03 opium kernel: [ 869.066701] ReiserFS: dm-2: Using r5 hash to sort names Mar 10 12:05:03 opium kernel: [ 869.066718] ReiserFS: dm-2: warning: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount. My /dev/rootvg/opt and /dev/rootvg/home were corrupt. Please note, this was after a successful shutdown - no power failures, no crashes, it all shutdown as fine as Scarlet Johanson I ran the fsck on opt and it said it need the --rebuild-tree option - which I did and which still didn't fix the problem. When you try to mount it says ~# mount /dev/rootvg/opt /opt/ mount: Operation not supported After a mkfs.reiserfs it works fine. On my home directory, it did a fsck.reiserfs --rebuild-tree -S /dev/rootvg/home Hours later, I could mount home, alas it only had one folder - "lost+found" Inside where all my files in this format 47417_47512 47466_47486 47466_48276 47472_47915 47483_48277 47489_47490 47489_47574 47491_47559 47491_5978 47499_48278 47527_47521 It appears the files are all there, just jumbled around. I started moving them back and thought "what if this happens again". So, I stopped, rebooted and it hit me again. I did a second --rebuild-tree -S and I then changed my /etc/fstab file to this /dev/mapper/rootvg-home /home reiserfs defaults 0 0 I haven't had it happen to my home again. Since the change, I haven't had any problems with my home partition, but I still get the problem on opt - so I simply commented it out in the /ect/fstab file. It appears there a boxing match between reiserfs and lvm and, what I am guessing is the superblocks. -- After Hardy Alpha5 upgrade lvm partitions fail to mount https://bugs.launchpad.net/bugs/200867 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
