Commit Graph

4 Commits

Author SHA1 Message Date
pjd
57ed96b72c Imagine a situation where:
# ls -ld /mnt/{foo,bar}
	drwxr-xr-x  3 root  wheel  512 Mar 16 06:56 /mnt/bar
	lrwxr-xr-x  1 root  wheel    3 Mar 16 12:10 /mnt/foo -> bar

	# grep /mnt/foo /etc/fstab
	/dev/da1	/mnt/foo	ufs	rw	0	0

Which means, we give symbolic link as a mount point to mount(8), but mount(8)
use realpath(3) before mounting the file systems, so we get:

	# mount | grep /dev/da1
	/dev/da1 on /mnt/bar (ufs, local)

Before the commit:

	# snapinfo /mnt/foo
	usage: snapinfo [-v] -a
	       snapinfo [-v] mountpoint
	# snapinfo /mnt/bar
	/mnt/bar/snap

This commit makes snapinfo(8) to first realpath(3) the given mount point and
now we have:

	# snapinfo /mnt/foo
	/mnt/bar/snap
	# snapinfo /mnt/bar
	/mnt/bar/snap
2007-03-16 12:36:54 +00:00
pjd
545f9291a9 Pass special device to the ufs_disk_fillout() function, instead of mount
point path. This way we properly handle the case when file system listed
in /etc/fstab was unmounted and another file system was mounted on the
same mount point.
2007-03-16 03:23:32 +00:00
hrs
fca73f2908 Fix version number when the feature was added.
Spotted by:	ceri
MFC after:	1 day
2006-03-23 07:55:33 +00:00
marks
2854e6f54b snapinfo -- show snapshot location on UFS file systems
Glanced over by: kan
Review by: ru (snapshot.8)
MFC: TBD
2005-07-20 18:59:25 +00:00