linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Strangenesses with snapshots, 0.9.1-beta6.
Date: Wed, 18 Apr 2001 12:15:09 -0600 (MDT)	[thread overview]
Message-ID: <200104181815.f3IIF9JW030481@webber.adilger.int> (raw)
In-Reply-To: <20010417234127.B3388@sistina.com> "from AJ Lewis at Apr 17, 2001 11:41:27 pm"

AJ writes:
> Are you sure those files were in a consistant state when you took the
> snapshot?  You really need to get your file system into a consistant state,
> otherwise the metadata could be partially written out when the snapshot is
> made.  There are hooks put into the 2.4x series kernels for ReiserFS to
> allow it to prepare for snapshots...but i don't think ext2 uses any
> mechanisms like this.  I don't know a whole lot about it, but that's what it
> looks like to me.

Well, before the LVM snapshot is created, it does a full sync of the device,
so the amount of metadata that could be out-of-date would be very small (if
any).

Granted, there is a possibility that the original data is corrupt, but 
Vegard reports everything OK on the original filesystem.  I assume that
e2fsck -f on the unmounted /dev/vg/nhome works OK?

> > cp: cannot stat `/mnt/backup/vegard/Mail/unix/openldap-general/314': Input/output error
> > cp: cannot stat `/mnt/backup/vegard/Mail/unix/openldap-general/315': Input/output error
> > cp: cannot stat `/mnt/backup/vegard/Mail/unix/openldap-general/316': Input/output error
> > cp: cannot stat `/mnt/backup/vegard/Mail/unix/openldap-general/317': Input/output error
> > 
> > [ *** This is another strangeness *** ]
> > middagspynten:/mnt/backup/vegard/Mail/unix/openldap-general# ls -l
> > .....
> > -rw-------    1 vegard   vegard       3454 Dec 11  1999 309
> > -rw-------    1 vegard   vegard       4530 Sep  9  1999 31
> > -rw-------    1 vegard   vegard       4147 Dec 11  1999 310
> > -rw-------    1 vegard   vegard       3294 Dec 11  1999 311
> > -rw-------    1 vegard   vegard       3452 Dec 11  1999 312
> > -rw-------    1 vegard   vegard       5775 Dec 13  1999 313
> > -rw-------    1 vegard   vegard       3292 Dec 22  1999 318
> > -rw-------    1 vegard   vegard       4318 Dec 22  1999 319
> > -rw-------    1 vegard   vegard       4384 Sep 11  1999 32

The same files with IO errors are those missing from the directory listing.
Based on the file timestamps, I would assume that these files have not
been changed in a long time, so it is not a metadata consistency issue.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

  reply	other threads:[~2001-04-18 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 20:08 [linux-lvm] Strangenesses with snapshots, 0.9.1-beta6 Vegard Engen
2001-04-18  4:41 ` AJ Lewis
2001-04-18 18:15   ` Andreas Dilger [this message]
2001-04-18 18:39     ` AJ Lewis

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=200104181815.f3IIF9JW030481@webber.adilger.int \
    --to=adilger@turbolinux.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;
as well as URLs for NNTP newsgroup(s).