Linux LVM users
 help / color / mirror / Atom feed
From: Thomas Ziegler <zie@codingtechnologies.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] kernel: zam-7001: io error in reiserfs_find_entry
Date: Fri Jan 11 04:52:02 2002	[thread overview]
Message-ID: <20020111114737.A22576@codingtechnologies.de> (raw)
In-Reply-To: <20020111103718.GA1274@tykepenguin.com>

On Fri, Jan 11, 2002 at 10:37:18AM +0000, Patrick Caulfield wrote:
> 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.
> 

Some Questions to LVM and snapshots:

- Do other filesystems cope in a better way with a full snapshot than reiserfs? 

- What's the preferred fs in conjunction with lvm?

- Is there a way to get the snapshot not destroyed if it is getting full?

Thanks in advance,
Thomas


-- 
Dr.-Ing. Thomas Ziegler            |
Senior Research Engineer           | Coding Technologies
phone: +49 (0) 911 92891 -27       | Deutschherrnstr. 15-19
fax:   +49 (0) 911 92891 -99       | D-90429 N�rnberg, Germany
mailto:zie@CodingTechnologies.com  | http://www.CodingTechnologies.com

  reply	other threads:[~2002-01-11  4:52 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 [this message]
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=20020111114737.A22576@codingtechnologies.de \
    --to=zie@codingtechnologies.de \
    --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