Date: Sun, 24 Feb 2008 19:38:17 +0100 From: =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> To: Guido Falsi <mad@madpilot.net> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: UFS snapshot weirdness Message-ID: <CE45BB81-E8B6-410C-9751-5D1770D7FD2C@anduin.net> In-Reply-To: <47C03FE5.8030703@madpilot.net> References: <79029E40-6E43-4482-8E39-D1DE49C8C53A@anduin.net> <200802122311.43247.doconnor@gsoft.com.au> <5B010AC7-C292-45E6-A109-20E39B370604@anduin.net> <200802131851.15014.doconnor@gsoft.com.au> <78796912-6D98-4433-A5C9-622854C7DFB2@anduin.net> <47C03FE5.8030703@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 23, 2008, at 4:46 PM, Guido Falsi wrote: > Eirik =D8verby wrote: > >> I read somewhere else about NFS issues on 7-RC* where snapshots =20 >> have been used. In particular - and this is something I'm seeing =20 >> too - changing the exports file or reloading mountd gives the =20 >> following in messages log: >> Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /=20 >> tmp: Invalid argument >> Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /=20 >> usr: Cross-device link >> Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /=20 >> var: Cross-device link >> Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /=20 >> export/home: Cross-device link >> Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /=20 >> opt: Cross-device link >> Can this be related? I'm starting to worry here - what will be the =20= >> long-term consequences if snapshots are stuck around in this =20 >> "invisible" state? Ok there is definitely something VERY fishy going on here. I have just removed a lot of data from one of the partitions where I =20 HAD snapshots (they are all gone now, since days). So freespace =20 initially goes up a lot, as expected, then drops to around what it was =20= before the deletion took place. There IS a snapshot being maintained =20 somewhere, even though I have deleted it (using rm -f). What can I do, =20= short of rebooting or remounting the filesystem?? This behavior is also seen on 6.2-RELEASE by the way; entirely =20 different hardware (32bit vs 64bit, scsi vs ide, etc.) /Eirik >> > > I have been experiencing these too. But it looks more like a bug in =20= > mountd, since it shows up only is snapshots are created with mount. =20= > If snapshots are created with mksnap_ffs this does not seem to show =20= > up. > > I still have to make more in depth experiments, but before =20 > experimenting by myself I'd like to have some more informed =20 > directions on what to experiment. > > --=20 > Guido Falsi <mad@madpilot.net> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org=20 > " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CE45BB81-E8B6-410C-9751-5D1770D7FD2C>