From: Chris Mason <mason@suse.com>
To: Ed Tomlinson <tomlins@CAM.ORG>
Cc: linux-lvm@sistina.com
Subject: [linux-lvm] Re: [OOPS] full snapshot (with test vfs locking patch for reiserfs snapshots in 11-pre)
Date: Wed, 10 Oct 2001 19:21:54 -0400 [thread overview]
Message-ID: <1114900000.1002756114@tiny> (raw)
In-Reply-To: <20011010212821.D540EB630@oscar.casa.dyndns.org>
On Wednesday, October 10, 2001 05:28:21 PM -0400 Ed Tomlinson <tomlins@CAM.ORG> wrote:
> Chris, with 2.4.11, your test vfs locking patch (manually fixing a reject) plus
> the second snapshot full patch with the addon from this message I have not been
> able to break things.
>
> If you are happy too, suggest you post the patches.
Good to hear Ed, many thanks. Would you mind running one extra
set of tests? I'm having problems with the system crashing/deadlocking
under high snapshot COW load. 10 concurrent writers onto the source
volume triggers it within 10-20 minutes. I'm using stress.sh,
but dbench should work too...I'm seeing this on pure rc4 (2.4.1[01],
and with my\x7f^\bzes).
Once this is worked out, I'll send everything in.
-chris
next prev parent reply other threads:[~2001-10-10 23:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011003230330.508E91104F@oscar.casa.dyndns.org>
[not found] ` <20011008012906.D790A11069@oscar.casa.dyndns.org>
[not found] ` <77260000.1002507094@tiny>
2001-10-08 15:53 ` [linux-lvm] [OOPS] full snapshot (with test vfs locking patch for reiserfs snapshots in 11-pre) Ed Tomlinson
2001-10-08 16:54 ` [linux-lvm] " Chris Mason
2001-10-08 17:05 ` Ed Tomlinson
2001-10-08 17:40 ` Chris Mason
2001-10-08 19:51 ` Chris Mason
2001-10-09 1:57 ` Ed Tomlinson
2001-10-09 2:29 ` Chris Mason
2001-10-09 11:42 ` Ed Tomlinson
2001-10-10 21:28 ` Ed Tomlinson
2001-10-10 23:21 ` Chris Mason [this message]
2001-10-11 0:37 ` Ed Tomlinson
2001-10-11 1:27 ` Chris Mason
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=1114900000.1002756114@tiny \
--to=mason@suse.com \
--cc=linux-lvm@sistina.com \
--cc=tomlins@CAM.ORG \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).