From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: dlarge-RrB2l6sP9Nll57MIdRCFDg@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: uuid for nilfs partition?
Date: Tue, 25 May 2010 00:33:45 +0900 (JST) [thread overview]
Message-ID: <20100525.003345.115737304.ryusuke@osrg.net> (raw)
In-Reply-To: <4BFA8D5B.6000700-RrB2l6sP9Nll57MIdRCFDg@public.gmane.org>
Hi,
On Mon, 24 May 2010 09:29:47 -0500, Darien Large wrote:
> I'm using nilfs2 for my /home directory, under Ubuntu 10.04 with kernel
> 2.6.32-22. I love it, but I'm having trouble mounting it through fstab
> consistently. How can I set a UUID for an nilfs volume? I've been unable
> to do so using any of the linux tools I'm aware of.
>
> --Darien Large
UUID is set when creating nilfs volume with mkfs.nilfs2 (or mkfs -t
nilfs2). But, the current standard mount program does not identify
the UUID of nilfs partitions.
Unfortunately, no UUID (nor label) tool is yet available for nilfs
though it's not time-consuming job.
The problem is that we were not able to promote nilfs to such standard
tools yet. Recently we had discussion on the procedure to do this,
but sorry, it seems still take a while by the time it becomes
available commonly.
Regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-24 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 14:29 uuid for nilfs partition? Darien Large
[not found] ` <4BFA8D5B.6000700-RrB2l6sP9Nll57MIdRCFDg@public.gmane.org>
2010-05-24 15:33 ` Ryusuke Konishi [this message]
[not found] ` <20100525.003345.115737304.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-05-24 16:11 ` Darien Large
2010-05-28 20:11 ` Jay Carlson
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=20100525.003345.115737304.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=dlarge-RrB2l6sP9Nll57MIdRCFDg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox