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 21:27:56 -0400 [thread overview]
Message-ID: <1148250000.1002763676@tiny> (raw)
In-Reply-To: <20011011003731.A9ADE160A8@oscar.casa.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Wednesday, October 10, 2001 08:37:31 PM -0400 Ed Tomlinson <tomlins@CAM.ORG> wrote:
> I just finished running about 40 mins of debench filling 3 1G snapshots.
> No stalls/opps. I am creating the snapshot with
>
> lvcreate -L1G -s -n snap /dev/lv/root /dev/hda3
>
> /dev/lv/root lives on hde. Does your snapshot live on the same physical
> disk as its source disk?
Yes, at least partly.
>
> Can you please send me the version of stress.sh you are using? I'll see
> if that triggers anything here.
Attached. I run stress.sh -n 10 -c (some ~40MB dir) -s /mntpoint.
Each process makes a local copy of the working dir, and verifies the
contents of the copy.
thanks,
Chris
[-- Attachment #2: stress.sh --]
[-- Type: application/x-sh, Size: 3126 bytes --]
prev parent reply other threads:[~2001-10-11 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 23:03 [BUG] opps in 2.4.11-pre2 + prempt patch Ed Tomlinson
2001-10-04 13:12 ` [reiserfs-list] " Chris Mason
[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
2001-10-11 0:37 ` Ed Tomlinson
2001-10-11 1:27 ` Chris Mason [this message]
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=1148250000.1002763676@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 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.