From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] kernel: zam-7001: io error in reiserfs_find_entry
Date: Fri Jan 11 04:38:02 2002 [thread overview]
Message-ID: <20020111103718.GA1274@tykepenguin.com> (raw)
In-Reply-To: <22543.1010745017@joergli.cocolab.de>
On Fri, Jan 11, 2002 at 11:30:17AM +0100, J?rgen Vollmer wrote:
>
> Hi everybody,
>
> I use kernel-source-2.4.16.SuSE-24.i386.rpm together with reiserfs and
> made a snapshot which I then tar'ed.
> Writing the tape seems to be ok. After that I did:
>
> tar --directory=/ --file=/dev/tape --compare
>
> and got the message (while working i.e. modifying the original filesystem)
>
> Message from syslogd@joergli at Fri Jan 11 10:57:19 2002 ...
> joergli kernel: zam-7001: io error in reiserfs_find_entry
>
>
> So it seems that the snapshot is full. Is that correct, or do I have a serious
> problem? Note: I'm doing my backups, so a dead backup is not a very good
> one :-)
Yes, your snapshot is full. When this happens LVM fails all I/O to the snapshot.
Unfortunatetly reiserfs doesn't not currently cope very well with I/O errors on
a device hence the message you saw.
You will need to allocate more space to the snapshot LV to get around this.
It's not a serious problem but if you are bothered by the oops I posted a
patch to workaround to the problem here:
http://lists.sistina.com/pipermail/linux-lvm/2001-November/009913.html
It's not great and it doesn't stop the full snapshot being unusable, but it does
stop the oopses.
patrick
next prev parent reply other threads:[~2002-01-11 4:38 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 [this message]
2002-01-11 4:52 ` Thomas Ziegler
2002-01-11 5:02 ` Patrick Caulfield
2002-01-11 8:39 ` Chris Mason
-- 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=20020111103718.GA1274@tykepenguin.com \
--to=caulfield@sistina.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