Re: XFS on top RAID10 with odd drives count and 2 near copies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 2/14/2012 3:05 AM, David Brown wrote:

> I believe that if you have XFS on LVM, then making a snapshot will first
> "freeze" the filesystem, take the snapshot, then "thaw" the filesystem.
>  This process will sync the system, flushing out outstanding writes, and
> delay new writes until the "thaw" - thus you get a bit better than a
> "power-off copy".  In particular, you don't get zeroed-out files no
> matter what you've done with your barrier settings.

xfs_freeze[1] was a feature/command carried over from IRIX to Linux
during the XFS port.  This functionality was later moved from the XFS
layer into the VFS layer.  Now FS freezing is fully automatic when an
LVM snapshot is taken.  Now in the VFS layer, this works with any
filesystem type, EXT2/3/4, Reiser, JFS, XFS.  I don't have the date or
kernel rev handy where this was integrated in mainline.  It's been at
least a couple/few years.  I'm not inclined to dig it up.


[1] xfs_freeze(8)

NAME
       xfs_freeze - suspend access to an XFS filesystem

SYNOPSIS
       xfs_freeze -f | -u mount-point

DESCRIPTION
       xfs_freeze suspends and resumes access to an XFS filesystem (see
xfs(5)).
[...]


-- 
Stan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[ATA RAID]     [Linux SCSI Target Infrastructure]     [Managing RAID on Linux]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device-Mapper]     [Kernel]     [Linux Books]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Photos]     [Yosemite Photos]     [Yosemite News]     [AMD 64]     [Linux Networking]

Add to Google Powered by Linux