fsnap(1M) is most woo-esque for backing up filesystems, in a
- snapshot filesystem
- dump filesystem to tape
- release snapshot
- check dump
kind of manner.
It does, however, have problems with realtime priority processes. If the executable of such a process resides on the filesystem being snapshotted, things don’t work:
snapshot error: File system could not be write locked
Quick solution: identify these processes and halt them across the snapshot:
# priocntl -d -i class RT
REAL TIME PROCESSES:
PID RTPRI TQNTM
577 0 0
In this case, pid 577 was xntpd(1M).
Perhaps a better attempt would be to temporarily jigger the priority away from realtime.
Leave a Reply
Recent articles
- cron
(Wednesday, 02. 24. 2010 – 6 Comments) - SOAP in unexpected “actually, quite easy” incident.
(Wednesday, 09. 30. 2009 – No Comments) - ipmitool for OSX
(Tuesday, 09. 29. 2009 – No Comments) - vxargs – visual parallel xargs
(Friday, 09. 18. 2009 – 1 Comment)
Archives
- February 2010
- September 2009
- August 2009
- January 2009
- September 2008
- August 2008
- July 2008
- May 2008
- April 2008
- February 2008
- January 2008
- November 2007
- October 2007
- September 2007
- August 2007
- December 2006
- November 2006
- August 2006
- June 2006
- May 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005