Re: massive LV corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 14, 2004 at 07:49:45AM -0700, Clint Byrum spake thusly:
> Hans Reiser has stated that this is because each filesystem has a lock 
> on it, so while writing to, say, /home/cvs, anybody else who wants to 
> write to /home/cvs will have to wait. We have a CVS server where the 

That's odd given that each hard drive can only physically write to one
place on the disk at a time anyhow due to head movement and that the
kernel caches the writes and lays them back out on the disk with some sort
of elevator algorithm.

> You said you were running 2.4.22.nptl or something.

Oops, right you are. That is what the box in question was and is running.
I was thinking of a different box with FC2 on it.

-- 
Tracy Reed                     The attachment is a digital signature.
http://copilotconsulting.com   More info: http://copilotconsulting.com/sig

Attachment: pgpnuRy677ZiF.pgp
Description: PGP signature

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux