All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshot file zombies
Date: Mon Dec  9 07:55:02 2002	[thread overview]
Message-ID: <20021209144653.B19400@sistina.com> (raw)
In-Reply-To: <19352.1039432905@joergli.cocolab.de>; from juergen@informatik-vollmer.de on Mon, Dec 09, 2002 at 12:21:45PM +0100

Jürgen,

those are Reiserfs errors telling that the filesystem isn't able to
search an entry by key. Could well be an io error on the snapshot LV but
then we should have a related entry in the syslog.

If you are able to read the snapshot fine (for eg. with 
(dd if=/dev/SNAPSHOT of=/dev/null bs=1024k), I assume a reiserfs error.

If reading the snapshot LV fails, let's go forward analyzing LVM, if not
there might be a reiserfs fix for that.

On Mon, Dec 09, 2002 at 12:21:45PM +0100, Jürgen Vollmer wrote:
> 
> Dear heinz,
> 
> "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
> > Can you find any nasty messages in your syslog related to the
> > access fault or _before_ you weren't able to access it?
> 
> the only obscure message I found was:
> 
> Dec  7 01:22:07 joergli kernel: vs-7000: search_by_entry_key: search_by_key returned item position == 0<4>vs-7000: search_by_entry_key: search_by_key returned item position == 0<4>vs-7000: search_by_entry_key: search_by_key returned item position == 0<4>zam-7001: io error in reiserfs_find_entry
> 
> Dec  7 01:22:07 joergli kernel: vs-7000: search_by_entry_key: search_by_key returned item position == 0<4>zam-7001: io error in reiserfs_find_entry
> 
> but the failure was around 15:00 on that day
> 
> Jürgen
> 
> -- 
> Dr.rer.nat. Juergen Vollmer, Viktoriastrasse 15, D-76133 Karlsruhe
> Tel: +49(721) 9204871 Fax: +49(721) 24874
> juergen@informatik-vollmer.de,vollmer@cocolab.de,Juergen.Vollmer@acm.org
> www.informatik-vollmer.de
> 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-12-09  7:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-07  6:52 [linux-lvm] snapshot file zombies Jürgen Vollmer
2002-12-09  4:46 ` Heinz J . Mauelshagen
2002-12-09  5:23   ` Jürgen Vollmer
2002-12-09  7:55     ` Heinz J . Mauelshagen [this message]
2003-01-04 11:03       ` Jürgen Vollmer

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=20021209144653.B19400@sistina.com \
    --to=mauelshagen@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 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.