On Thu, Nov 28, 2013 at 09:52:37AM +0100, Vratislav Podzimek wrote:
On Wed, 2013-11-27 at 11:54 -0800, Brian C. Lane wrote:
> From: "Brian C. Lane" <bcl(a)redhat.com>
>
> ---
> blivet/formats/fs.py | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/blivet/formats/fs.py b/blivet/formats/fs.py
> index 43f9d44..103717e 100644
> --- a/blivet/formats/fs.py
> +++ b/blivet/formats/fs.py
> @@ -1030,8 +1030,6 @@ class BTRFS(FS):
> _linuxNative = True
> _maxLabelChars = 256
> _supported = True
> - _dump = True
> - _check = True
> _packages = ["btrfs-progs"]
> _minSize = 256
> _maxSize = 16 * 1024 * 1024
> @@ -1191,8 +1189,6 @@ class XFS(FS):
> _formattable = True
> _linuxNative = True
> _supported = True
> - _dump = True
> - _check = True
> _packages = ["xfsprogs"]
> _infofs = "xfs_db"
> _defaultInfoOptions = ["-c", "\"sb 0\"",
"-c", "\"p dblocks\"",
Is this really still true? I've just moved my Fedora 20 from an HDD to
an SSD and from ext4 to xfs yesterday and boot time fsck on xfs worked
well (even if I didn't expect it to). Also, now that xfs is the default
filesystem for RHEL I think it would have to support that.
Yes. According to the manpage the fsck.xfs that is run at boot time is a
noop. It does the checking at mount time instead.
--
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)