From: Tracy R Reed <treed@copilotconsulting.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] massive LV corruption
Date: Tue, 14 Sep 2004 13:06:24 -0700 [thread overview]
Message-ID: <20040914200624.GE13649@copilotconsulting.com> (raw)
In-Reply-To: <51D9A0D8-065D-11D9-BB02-000A95730E92@spamaps.org>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
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 #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-14 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 11:08 [linux-lvm] massive LV corruption Tracy R Reed
2004-09-11 11:25 ` Tracy R Reed
2004-09-14 0:46 ` Tracy R Reed
2004-09-14 5:45 ` Clint Byrum
2004-09-14 12:45 ` Tracy R Reed
2004-09-14 14:49 ` Clint Byrum
2004-09-14 20:06 ` Tracy R Reed [this message]
2004-09-14 20:41 ` Clint Byrum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040914200624.GE13649@copilotconsulting.com \
--to=treed@copilotconsulting.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.