From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH 0/2] allow UUID changes on V5/CRC filesystems
Date: Fri, 08 May 2015 15:40:54 -0500 [thread overview]
Message-ID: <554D1F56.7030209@redhat.com> (raw)
Ok, here's the next round. This has been through some degree of testing,
though I still probably owe some xfstests testcases.
Dave, in the end I went ahead and kept the sb_uuid name and meaning
in the same superblock location; this does mean we touch all verifiers
etc, but it makes for more consistency, IMHO.
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-05-08 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 20:40 Eric Sandeen [this message]
2015-05-08 20:48 ` [PATCH 1/2] xfs: create new metadata UUID field and incompat flag Eric Sandeen
2015-05-11 16:14 ` Brian Foster
2015-05-11 16:52 ` Eric Sandeen
2015-05-11 21:49 ` Dave Chinner
2015-05-11 23:50 ` Eric Sandeen
2015-05-12 1:58 ` Dave Chinner
2015-05-12 11:11 ` Brian Foster
2015-05-08 20:59 ` [PATCH 2/2] xfsprogs: Add new sb_meta_uuid field, and userspace tools to manipulate it Eric Sandeen
2015-05-08 21:14 ` Eric Sandeen
2015-05-08 21:49 ` [PATCH 2/2 V2] " 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=554D1F56.7030209@redhat.com \
--to=sandeen@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox