Date: Tue, 12 Nov 2002 16:56:17 -0500 (EST) From: Phil Budne <phil@ultimate.com> To: FreeBSD-gnats-submit@FreeBSD.org Cc: phil@ultimate.com Subject: gnu/45246: tar --listed-incremental fails for Solaris NFS filesystems Message-ID: <200211122156.gACLuHFZ000349@peecee.ultimate.com>
next in thread | raw e-mail | index | archive | help
>Number: 45246 >Category: gnu >Synopsis: tar --listed-incremental fails for Solaris NFS filesystems >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 12 14:00:05 PST 2002 >Closed-Date: >Last-Modified: >Originator: Phil Budne >Release: FreeBSD 4.7-STABLE i386 >Organization: Consultant >Environment: System: FreeBSD peecee.ultimate.com 4.7-STABLE FreeBSD 4.7-STABLE #17: Mon Oct 21 13:15:40 EDT 2002 phil@peecee.ultimate.com:/home/src/sys/compile/A900 i386 >Description: Attempting to do incrementals of an filesystem NFS mounted from Solaris 2.4 (SunOS 5.4) always dumps all the files. (I did it because Solaris 2.4 doesn't support large files, but does support large filesystems, so sending the data over the network using rsh or rmt failed). >How-To-Repeat: tar -cvf output -g listfile /nfs/solaris24/filesystem >Fix: The GNU TAR check for NFS filesystems fails; It only checks the high order bit of st_dev, which isn't set in Solaris' fsid's (but does work for SunOS4, and presumably other implementations). Typical values for st_dev: 0x31eff9d 0x31eff9b. Checking if any of the bits in the high nybble helped, but not sure if that's right. Checking if minor(st_dev) == 0xff seems to work also. Would be nifty to have some "standard" (hah!) way to check! >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211122156.gACLuHFZ000349>