From: Michael Marxmeier <mike@msede.com>
To: Andi Kleen <ak@suse.de>
Cc: "'linux-lvm@msede.com'" <linux-lvm@msede.com>
Subject: Re: [linux-lvm] LVM seems to break tar and cp "stay-local" option s
Date: Wed, 26 Jan 2000 03:52:14 +0100 [thread overview]
Message-ID: <388E615E.308E3B68@msede.com> (raw)
In-Reply-To: 20000126015911.A2968@gruyere.muc.suse.de
Andi Kleen wrote:
> This could explain some NFS failures too. dev_t is part of the nfs
> filehandle given out by knfsd, when two LVs with different file systems
> have the same dev_t it may chose another file with the same inode number.
> Normally it does not matter because knfsd maintains a fh cache that has the
> right file, but when the cache overflows or the nfs server is rebooted
> it could access the file with the same ino on the wrong LV afterwards :/
st_dev looks fine to me (st_rdev looks inconsistent with libc5 for
non dev files).
SuSE 6.3 (glibc 2.1.2), LVM 0.8i:
$ df /usr /var
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/vg00/usr 2031360 783652 1142852 41% /usr
/dev/vg00/var 253920 30048 210768 12% /var
$ ./stat /usr/bin/host /var/tmp/vi.recover
dev=3a00 ino=33505 mode=100755 rdev=0 /usr/bin/host
dev=3a02 ino=32809 mode=41777 rdev=0 /var/tmp/vi.recover
$ ls -l /dev/vg00
...
brw-r----- 1 root root 58, 0 Dec 23 01:39 usr
brw-r----- 1 root root 58, 2 Dec 23 01:39 var
SuSE 5.x (libc5), LVM 0.7:
$ df /mnt3
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/vg00/lvol1 4098376 3605796 281024 93% /mnt3
$ ./stat /mnt3/db/db01.vol
dev=3a00 ino=384770 mode=100600 rdev=84b /mnt3/db/db01.vol
$ ls -l /dev/vg00
...
brw-r----- 1 root root 58, 0 Nov 19 08:26 lvol1
Michael
--
Michael Marxmeier Marxmeier Software AG
E-Mail: mike@msede.com Besenbruchstrasse 9
Phone : +49 202 2431440 42285 Wuppertal, Germany
Fax : +49 202 2431420 http://www.msede.com/
next prev parent reply other threads:[~2000-01-26 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-25 20:19 [linux-lvm] LVM seems to break tar and cp "stay-local" option s Steve_J_Brueggeman
2000-01-26 0:59 ` Andi Kleen
2000-01-26 2:52 ` Michael Marxmeier [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-25 20:33 Steve_J_Brueggeman
2000-01-25 19:07 Jakma, Paul
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=388E615E.308E3B68@msede.com \
--to=mike@msede.com \
--cc=ak@suse.de \
--cc=linux-lvm@msede.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.