[Summary] fssnap: ioctl: error 16: Device busy
From: Chris Hoogendyk (hoogendyk_at_bio.umass.edu)
Date: 05/31/05
- Previous message: jason kappy: "BSM auditing error."
- In reply to: Chris Hoogendyk: "fssnap: ioctl: error 16: Device busy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 31 May 2005 16:47:12 -0400 To: Sun Managers List <sunmanagers@sunmanagers.org>
Two replies. Thanks to <Chris_Sellers@adp.com> and Bill R. Williams
<brw@etsu.edu>
suggestion for `devfsadmd -C -v` did nothing.
suggeston to `umount /dev/fssnap/0` worked. for some reason the mounted
snap shot file system was an anomoly left over from the killed process.
once it was umounted, `fssnap -d /` worked. then `fssnap -i` showed no
snap shots existing.
I guess from fssnap's perspective, being mounted is busy; whereas, from
lsof's perspective, it is assumed to be mounted, but no one was
accessing it, so it wasn't busy.
anyway, ... back in business.
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology Department
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<hoogendyk@bio.umass.edu>
---------------
Chris Hoogendyk wrote:
> during debugging of a script, I interrupted it with a control c. that
> was last Friday. since then, I have not been able to remove the snap
> shots that were created. I get:
>
> # fssnap -F ufs -d /
> fssnap: ioctl: error 16: Device busy
>
> I have done a variety of things trying to figure this out, including
> googling, man pages, and sunsolve. First, the information:
>
> # /usr/lib/fs/ufs/fssnap -i
> Snapshot number : 0
> Block Device : /dev/fssnap/0
> Raw Device : /dev/rfssnap/0
> Mount point : /
> Device state : active
> Backing store path : /export/home/scratch <UNLINKED>
> Backing store size : 3328 KB
> Maximum backing store size : Unlimited
> Snapshot create time : Fri May 27 16:13:35 2005
> Copy-on-write granularity : 32 KB
> Snapshot number : 1
> Block Device : /dev/fssnap/1
> Raw Device : /dev/rfssnap/1
> Mount point : /export/home
> Device state : active
> Backing store path : /var/scratch <UNLINKED>
> Backing store size : 2144 KB
> Maximum backing store size : Unlimited
> Snapshot create time : Fri May 27 16:13:50 2005
> Copy-on-write granularity : 32 KB
>
> # df -k
> Filesystem kbytes used avail cap Mounted on
> <snip>
> /dev/fssnap/0 8404388 1672809 6647536 21% /tmp/.rlg.YZaGmz/.rlg.YZaGmz
> /dev/fssnap/1 984861 1693 924077 1% /tmp/.rlg.BkaOpz/.rlg.BkaOpz
>
>
> I've tried several variations with lsof checking for processes that
> might have an open file on the snapshot or have the snapshot device or
> mount point open. All come up blank.
>
>
> I've also looked for zombie processes that might be connected with the
> ufsdump commands that were running. As I recall, I had to kill the
> ufsdump last Friday. There is nothing running now related to that and
> there are no processes that began on Friday except devfsadmd. I'm not
> sure I get that. On my other system the date on that process matches the
> system boot date. This system was booted several weeks ago, but the
> devfsadmd process date is Friday.
>
>
> I don't really want to reboot, because several critical network
> processes are running on this server. However, if no one can come up
> with a better idea, then I will reboot. Need backups.
>
>
> TIA
>
>
>
> ---------------
>
> Chris Hoogendyk
>
> -
> O__ ---- Systems Administrator
> c/ /'_ --- Biology Department
> (*) \(*) -- 140 Morrill Science Center
> ~~~~~~~~~~ - University of Massachusetts, Amherst
>
> <hoogendyk@bio.umass.edu>
>
> ---------------
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
- Previous message: jason kappy: "BSM auditing error."
- In reply to: Chris Hoogendyk: "fssnap: ioctl: error 16: Device busy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]