From: Linda Walsh <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 0/2 V3] allow UUID changes on V5/CRC filesystems
Date: Wed, 03 Jun 2015 04:14:18 -0700 [thread overview]
Message-ID: <556EE18A.1080606@tlinx.org> (raw)
In-Reply-To: <55525356.1020807@sandeen.net>
Eric Sandeen wrote:
> Final version? This has been through some degree of testing, by changing
> the UUID after a CRC mkfs, and re-setting it in between two xfs_repair runs
> before and after each test in the testsuite.
---
I think I see my problem.
Is there some strong technical reason why 'crc' has to
be on to get -finobt=1 && ftype=1. I'd like to try the latter two
features, but the 'crc' stuff has me a bit bugged -- for unanticipated
reasons like not being able to set the UUID (I so very often hit
those corner cases...*lucky-me*).
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-03 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 19:24 [PATCH 0/2 V3] allow UUID changes on V5/CRC filesystems Eric Sandeen
2015-05-12 19:27 ` [PATCH 1/2] xfs: create new metadata UUID field and incompat flag Eric Sandeen
2015-05-14 13:36 ` Brian Foster
2015-05-14 22:36 ` Dave Chinner
2015-05-14 22:55 ` [PATCH 1/2 V4] " Eric Sandeen
2015-05-12 19:30 ` [PATCH 2/2] xfsprogs: Add new sb_meta_uuid field, update userspace tools to manipulate it Eric Sandeen
2015-05-14 13:39 ` Brian Foster
2015-05-14 16:29 ` Eric Sandeen
2015-05-14 21:54 ` [PATCH 2/2 V4] " Eric Sandeen
2015-05-14 23:00 ` [PATCH 2/2 V5] " Eric Sandeen
2015-05-18 14:35 ` Brian Foster
2015-06-03 11:14 ` Linda Walsh [this message]
2015-06-03 20:31 ` [PATCH 0/2 V3] allow UUID changes on V5/CRC filesystems Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=556EE18A.1080606@tlinx.org \
--to=xfs@tlinx.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.