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
- MySQL replication health
(Tuesday, 09. 30. 2008 – No Comments) - Firewalls
(Friday, 09. 5. 2008 – No Comments) - Using Single Sign-On To Integrate Ning With An External Site
(Wednesday, 08. 20. 2008 – No Comments) - High Availability Rails Cluster
(Tuesday, 08. 19. 2008 – No Comments)