[Top] [All Lists]

Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root)

To: 694624@xxxxxxxxxxxxxxx
Subject: Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root)
From: Pat Emblen <support@xxxxxxxxxxxxxxxx>
Date: Mon, 03 Dec 2012 10:31:08 +1100
Organization: Talbragar Computers
Reply-to: Pat Emblen <support@xxxxxxxxxxxxxxxx>, 694624@xxxxxxxxxxxxxxx
Resent-cc: XFS Development Team <xfs@xxxxxxxxxxx>
Resent-date: Sun, 02 Dec 2012 23:45:05 +0000
Resent-from: Pat Emblen <support@xxxxxxxxxxxxxxxx>
Resent-message-id: <handler.694624.B694624.13544916421877@xxxxxxxxxxxxxxx>
Resent-sender: Debian BTS <debbugs@xxxxxxxxxxxxxxxxxxxx>
Resent-to: debian-bugs-dist@xxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.10) Gecko/20121027 Icedove/10.0.10
Well it's your call, but I'll make my case for changing it.
- I think it is very dangerous default behaviour, particularly in scripts as it can prevent
the possibility of logging in to unfreeze a frozen root.
- The docs all strongly imply that it operates on mountpoints, so surely not many people
would have diliberately used it on general paths?"
        xfs_freeze -f | -u mount-point"
"The mount-point argument is the pathname of  the  directory  where  the
       file system  is  mounted."
- Because of the name and the wording of the man page, you don't expect xfs_freeze to freeze an ext4 file system that isn't even mounted on the path you pass to it?! - It's logical to have it work on mountpoints only. You wouldn't expect umount or fdisk to
work the same way? Do any other partition level tools work this way?
- At the very least I would expect it to require a 'force' option if it was going to freeze
the root system.


<Prev in Thread] Current Thread [Next in Thread>