xfs
[Top] [All Lists]

Re: Filesystem on XFS partition no longer accessible afterwriting

To: Jurgen Kramer <GTM.Kramer@xxxxxxxxxxxx>
Subject: Re: Filesystem on XFS partition no longer accessible afterwriting
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Sat, 30 Jun 2001 16:20:47 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <3B3DE03C.4854A10E@inter.nl.net>
References: <4.3.2.7.2.20010630154857.03910850@pop.xs4all.nl>
Sender: owner-linux-xfs@xxxxxxxxxxx
At 16:20 30-6-2001 +0200, Jurgen Kramer wrote:
Seth Mos wrote:

> Do you have problems writing or reading from other applications?

What compiler did you use for compiling your kernel?

Yes, any application writing to the partition makes the partition unusable.
Reading doesn't give any problems.

>Can you give some statistics about your system and disk configuration?
> Any used hdpram parameters or mount options?

From the top of my head:

BP6 with dual 500Mhz Celeron / 192MB mem
HDD on HPT366 controller
Red Hat 7.0
kernel 2.4.6pre5-XFS (latest CVS)
no hdparm parameters of special mount options

N.b. this setup did work for a long time running Linux-XFS from SGI CVS. But
I didn't use
this system for a while only updating the kernel from CVS every one and a
while.

The setup should be ok.

> It still should work. Can you replicate this with an older kernel?
> And what kernel are you running now?

I'll check further in a moment. Currently the system is not accessible at
all.
As it doesn't have a keyboard or monitor so I have to connect these to see
what's really happening.

The only think that comes up at the moment is kernel compiled with gcc instead of kgcc
You could try checking the fs with xfs_repair to see if something is wrong.


Bye
--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.


<Prev in Thread] Current Thread [Next in Thread>