You are not logged in.

#1 2007-12-05 17:25:11

EtherNut
Member
Registered: 2007-09-29
Posts: 8

XFS Root Filesystem on LVM Stripe - Corruption

I want to create a LVM Stripe across two SATA drives.  The problem I keep running into is, on boot,  arch reports that a fsck needs to be run on the root filesystem, so it mounts it read only and allows me to type in the root password to get shell access.   This all happens after I do the initial arch install, reboot, log in normally, do a pacman -Syu, reboot. 

Here's what I have and what I did...

I have two 320G SATA Drives plugged into my system board (an ABIT AN-M2HD).  My Bios is set to "AHCI Linux" for the SATA mode.

Boot the latest Arch CD install at command prompt:

cfdisk /dev/sda
create 125M Partition (for /boot)        /dev/sda1
create 319G Partition                      /dev/sda2

cfdisk /dev/sdb
create 320G Partition                     /dev/sdb1

lvm pvcreate /dev/sda2 /dev/sdb1

lvm vgcreate lvmgrp0 /dev/sda2 /dev/sdb1

lvm lvcreate -i2 -I4 -L1G -nswap lvmgrp0
lvm lvcreate -i2 -I4 -L594G -nroot lvmgrp0

/arch/setup  (I'm going to abbreviate this)
Hard Drive Setup (chose option 3)
    Set swap to swap LV
    Set root to root LV (xfs)
    Set /dev/sda1 to /boot (ext3)

/etc/rc.conf USE LVM="YES"
Kerel Params = Boot from LVM Support? I answer Yes
Grub Looks Good.


Everything seemingly installs fine, I can reboot and arch comes right up.  But after I do pacman -Syu everything goes to pot.

I suspect I have something wrong in alignment between the LVM stripe and XFS, but dont know..

alternately, should I set my LVM Stripe Size to a value larger than 4?  I thought since on i686 max XFS block size is 4096 (4K) then they should match.  Any thoughts on this?

help! ;-)

Ether..

Offline

#2 2008-01-29 14:52:51

EtherNut
Member
Registered: 2007-09-29
Posts: 8

Re: XFS Root Filesystem on LVM Stripe - Corruption

I just wanted to add an update.  It wasn't a LVM issue, it was a XFS issue.

I went to Arch 64 bit for a while and everything (above) worked just fine.. The usability and Lib32 issues with 64 bit lost it's luster and last weekend I went back to 32 bit Arch.

In going back to 32 bit I followed my procedure above for partitioning just as I had with the 64 bit version and after rebooting from the install and updating packman, the same thing occurred, the file system would start to corrupt, pacman would complain that libraries were truncated and so forth.    After reboot, the /root partition would not mount read/write because it was not clean...

I reinstalled Arch 32 bit 6 times on Saturday trying various things in a scientific way and came to this conclusion:

__and I have no idea why__, but when I use the XFS file system on an install with Arch 32 bit, it hoses up.  "Your Crazy" you might say, but trust me I've tried it different ways more than a dozen times.  (I'm no n00b either, I've been an RHCE since 2003 and a daily Linux user since 1999.)  Seems crazy, but XFS was a constant in all of my testing.  The only thing I can figure is that it's my hardware and that's just a guess.  64 bit worked without a hitch with XFS.  I even got desperate and installed / on a lone 60 gig partition (/dev/sda1) completely deleting all LVMs and it still corrupted with XFS and 32 bit

The Solution?

I used JFS.  I have created the LVM Stripe as I have described above and it works great.  No issues.

Weird..

For the sake of knowledge I have a:

AMD 5000+ Black Edition CPU
Abit AN-M2HD Motherboard
2 Gig Dual Channel RAM (2x1Gb)
2 320 Gig SATA Drive
1 SATA DVD Writer


-Ether..

Last edited by EtherNut (2008-01-29 14:54:01)

Offline

Board footer

Powered by FluxBB