Date: Thu, 11 Nov 2004 20:07:01 +0100 (CET)
From: Jan Derfinak <ja@mail.upjs.sk>
To: Melissa Terwilliger <techess@umich.edu>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Xfs partition info seems to be lost on reboot
In-Reply-To: <BDB8DF2A.230B%techess@umich.edu>
Message-ID: <Pine.LNX.4.58.0411111927010.10840@alienAngel.home.sk>
References: <BDB8DF2A.230B%techess@umich.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk
Content-Length: 1026
Lines: 30

On Thu, 11 Nov 2004, Melissa Terwilliger wrote:

> zcat /proc/config.gz | grep CONFIG_LBD
> CONFIG_LBD=y
> 
> So I do have that set.  Should I have that unset do you think?

I think that there is no difference on 64-bit system. You can leave it on.
I propose to use original SLES9 kernel if it is possible. It is well tested
and approved by many companies.

> 
> >Is there possibility that parted changes only kernel idea about partition
> >table but not real disk layout? Did you try fdisk?
> 
> I have not used fdisk because I was told that it would work properly on
> disks over 2TB, the 3ware company suggested parted instead.
> 
> We have two identical machines setup.  I think I'm going to Try RedHat WS3
> and see if I have a similar problem there.  It might just be a problem with
> the 3Ware card or drivers.

Simplest thing you can do is to use fdisk and also look to
/proc/partitions before/after reboot like Eric mentioned. Please tell me if
there is any diffence if you use fdisk or SLES9 kernel.

					jan

--