[prev in list] [next in list] [prev in thread] [next in thread] 

List:       redhat-linux-cluster
Subject:    Re: [Linux-cluster] [PATCH] fsfreeze: suspend and resume access to
From:       Masatake YAMATO <yamato () redhat ! com>
Date:       2010-05-13 7:33:13
Message-ID: 20100513.163313.67205054690538917.yamato () redhat ! com
[Download RAW message or body]

Hi,

(The disscussion can be found at
 http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/3181/focus=3193)

> Hello.
> 
> I understand reason when it use with device-mapper.
> I think, fsfreeze command need for filesystem on physical block device without device-mapper.
> For example, by storage controller based LUN snapshot.
> 
> # fsfreeze -f /data
> # ssh root@192.168.0.1 "take snapshot lun0"
> # fsfreeze -u /data
> 
> * /data is mounted physical block device(/dev/sdb1)

As Hajime wrote, taking snapshot in physical storage level is popular
situation. It seems that xfs_freeze can be used for the purpose but
the name `xfs_freeze' gives the impression that the command is only 
for xfs. 

My argument can be applicable to gfs2_tool, too.  "gfs2_tool freeze"
also does ``ioctl(fd, FIFREEZE, 0)''.


One of the solution is to add xxx_freeze for each file system implementation
which has freeze/unfreeze methods to eash util-xxx, xxx-progs or xxx-utils. 
e.g. Adding ext4_freeze or ext3_freeze command to e2fsprogs package.

However, I think this is not good idea. Linux provides file system neutral
interface already. So it is better to have file system neutral command(fsfreeze)
and the command is included in file system neutral package, util-linux-ng.

Masatake YAMATO

--
Linux-cluster mailing list
Linux-cluster@redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster
[prev in list] [next in list] [prev in thread] [next in thread]