[linux-lvm] LVM seems to break tar and cp "stay-local" option s

Andi Kleen ak at suse.de
Wed Jan 26 00:59:11 UTC 2000

On Tue, Jan 25, 2000 at 02:19:21PM -0600, Steve_J_Brueggeman at notes.seagate.com wrote:
> Well, a quick of the tar source code reveals that they're using a stat(2) and
> checking
> parent_device != current_stat.st_dev
> to determine if the filesystem has changed.
> I just did a stat(1) on some files, (using LVM 0.7), and it always returns a
> minor number of 0, no matter what Logical Volume the file I checked lives on.
> Then again, I got the same result on files that reside on plain SCSI partitions
> (I have root and /usr on /dev/sda1 and /dev/sda3 respectively)
> System is RedHat 5.2, running linux-2.2.14 with LVM patches.
> On a RedHat 6.0 system running linux-2.3.40 W/O LVM patches, /usr/bin/stat
> returned expected device numbers.
> I need to look into this a bit further.  More to come....

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 :/


More information about the linux-lvm mailing list