From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] kernel: zam-7001: io error in reiserfs_find_entry
Date: Fri Jan 11 08:39:02 2002 [thread overview]
Message-ID: <51880000.1010759924@tiny> (raw)
In-Reply-To: <20020111110146.GE1274@tykepenguin.com>
On Friday, January 11, 2002 11:01:46 AM +0000 Patrick Caulfield
<caulfield@sistina.com> wrote:
> On Fri, Jan 11, 2002 at 11:47:37AM +0100, Thomas Ziegler wrote:
>>
>> Some Questions to LVM and snapshots:
>>
>> - Do other filesystems cope in a better way with a full snapshot than
>> reiserfs?
I've started cleaning these and a few other io related errors up, this
won't be an open issue much longer.
-chris
next prev parent reply other threads:[~2002-01-11 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 4:31 [linux-lvm] kernel: zam-7001: io error in reiserfs_find_entry Jürgen Vollmer
2002-01-11 4:38 ` Patrick Caulfield
2002-01-11 4:52 ` Thomas Ziegler
2002-01-11 5:02 ` Patrick Caulfield
2002-01-11 8:39 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 11:31 Stephenson, Dale
2002-01-11 11:40 ` Patrick Caulfield
2002-01-11 11:58 ` 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=51880000.1010759924@tiny \
--to=mason@suse.com \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox