From: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Inquiry: disk format change in the future
Date: Wed, 19 Aug 2009 22:55:39 -0500 [thread overview]
Message-ID: <4A8CC93B.9090904@redhat.com> (raw)
In-Reply-To: <20090820.112237.04623349.ryusuke-sG5X7nlA6pw@public.gmane.org>
Ryusuke Konishi wrote:
> (reply added to "Yann E. MORIN")
>
> Hi,
> On Wed, 19 Aug 2009 11:31:56 +0200, "Yann E. MORIN" wrote:
>> Hello All!
>>
>> I've searched the archives, but could not find the answer to the
>> following questions:
>>
>> - will there be, or what is the probability of, a disk format change
>> in the near future (few months)?
>
> We still have some possibilities for the format change at this time.
>
> Basically I intend to keep the disk format, but some new features like
>
> - Extended attributes, ACLs
> - Rollback
> - Checkpoint based remote replication
>
> may require it. So far, we haven't seen any specific requisition.
>
Do you expect that any of the changes may impact the ability of
utilities such as blkid or file to recognize a nilfs filesystem?
I'd happily write patches for those utilities to add nilfs recognition
if you think there is a stable fingerprint that can be recognized.
Thanks,
-Eric
next prev parent reply other threads:[~2009-08-20 3:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 10:17 Inquiry: disk format change in the future Yann E. MORIN
[not found] ` <20090820002457.A0C0520E21-lhVA/uj0YcqwblfueUDqnA@public.gmane.org>
2009-08-20 2:22 ` Ryusuke Konishi
[not found] ` <20090820.112237.04623349.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-20 3:55 ` Eric Sandeen [this message]
[not found] ` <4A8CC93B.9090904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-08-21 3:57 ` Ryusuke Konishi
[not found] ` <20090821.125734.96697535.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-21 4:04 ` 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=4A8CC93B.9090904@redhat.com \
--to=sandeen-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
/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.