Christoph,
Maybe I've found an event that triggers the fault.
If I do xfs_fsr (file system optimizer program for XFS) and then
xfs_check on several filesystems, I've found several times an error
reported by xfs_check on this filesystem, the message is:
bad nblocks 2 for inode 1026325, coun
Christoph,
Le 17.09.2005 17:14:28, Christoph Hellwig a écrit :
On Sat, Sep 17, 2005 at 09:33:06AM +, Jean-Luc Coulon (f5ibh)
wrote:
> Le 17.09.2005 11:18:02, Christoph Hellwig a ?crit?:
> >This looks like a typical corruption caused by not turning off the
> >write cache on your disks. Is th
On Sat, Sep 17, 2005 at 09:33:06AM +, Jean-Luc Coulon (f5ibh) wrote:
> Le 17.09.2005 11:18:02, Christoph Hellwig a ?crit?:
> >This looks like a typical corruption caused by not turning off the
> >write cache on your disks. Is the write cache on your disk on or
> >off?
>
> The disks are SATA d
Le 17.09.2005 11:18:02, Christoph Hellwig a écrit :
This looks like a typical corruption caused by not turning off the
write cache on your disks. Is the write cache on your disk on or
off?
The disks are SATA disks (MAxtom Diamondmax 9, 80GB) and I've not found
any way to turn ir on/off via h
This looks like a typical corruption caused by not turning off the
write cache on your disks. Is the write cache on your disk on or
off?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: linux-source-2.6.12
Version: 2.6.12-6
Severity: normal
Hi,
I'm not sure the kernel is responsible of this problem, this can be lvm as well.
I've 2.6.12 with lvm over a software raid1.
All the filesystems are xfs.
The architecture is X86_64 on an athlon 64 3500+. The system has been crea
6 matches
Mail list logo
