linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
	"Ext4 Developers List" <linux-ext4@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/3] mke2fs: print extra information about existing ext2/3/4 file systems
Date: Tue, 6 May 2014 09:44:55 +0200	[thread overview]
Message-ID: <20140506074455.GB29151@x2.net.home> (raw)
In-Reply-To: <20140505183253.GL22287@thunk.org>

On Mon, May 05, 2014 at 02:32:53PM -0400, Theodore Ts'o wrote:
> >  BTW, the current trend is to use GPT partition types to identify
> >  purpose of the partition filesystem (for example extra GUID for
> >  /home). It's FS independent solution and it allows use the right
> >  filesystems for the right mountpoints. It's very attractive for
> >  example for virtual images where you don't have to setup fstab and
> >  identify FS, but you still have (for example) /home on the right
> >  place.
> 
> But a partition only gets one GUUID and one partition type.  So are
> you saying that the GUUID partition type would be used to indicate the
> concept of "this is the file system for /home", *instead* of "this is
> an btrfs file system" or "this is an ext4 file system"?

 Yes, GPT partition has two UUIDs, 
 
   - UUID = an unique partition identifier
   - GUID = partition type identifier

 I talked about the type (GUID). Note that this concept is just
 another point of view how to mount partitions, I don't think it will
 be a mainstream solution for standard machines. Now it's supported by
 systemd. More details:

  http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/
 

 For old good fstab you can use PARTUUID= to identify partitions and
 to bypass filesystem specific identifiers. In this case it's unique 
 partition identifier, no partition type.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2014-05-06  7:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 13:04 [PATCH 1/3] mke2fs: print a message when creating a regular file Theodore Ts'o
2014-05-05 13:04 ` [PATCH 2/3] mke2fs: print extra information about existing ext2/3/4 file systems Theodore Ts'o
2014-05-05 13:45   ` Lukáš Czerner
2014-05-05 14:04     ` Theodore Ts'o
2014-05-05 14:17       ` Lukáš Czerner
2014-05-05 14:28       ` Theodore Ts'o
2014-05-05 14:38         ` Lukáš Czerner
2014-05-05 14:44           ` Theodore Ts'o
2014-05-05 14:51             ` Lukáš Czerner
2014-05-05 14:57               ` Theodore Ts'o
2014-05-05 16:25                 ` Andreas Dilger
2014-05-05 17:50               ` Karel Zak
2014-05-05 18:32                 ` Theodore Ts'o
2014-05-06  7:44                   ` Karel Zak [this message]
2014-05-05 16:30             ` Andreas Dilger
2014-05-05 13:04 ` [PATCH 3/3] mke2fs: check for a partition table and warn if present Theodore Ts'o
2014-05-05 13:52   ` Lukáš Czerner
2014-05-05 13:58     ` Theodore Ts'o
2014-05-05 14:11       ` Lukáš Czerner
2014-05-05 14:20         ` Theodore Ts'o
2014-05-06 12:20           ` Karel Zak
2014-05-06 12:52             ` Lukáš Czerner
2014-05-05 13:41 ` [PATCH 1/3] mke2fs: print a message when creating a regular file Lukáš Czerner
2014-05-05 13:52   ` Theodore Ts'o
2014-05-05 14:04     ` Lukáš Czerner
2014-05-05 14:46     ` Eric Sandeen
2014-05-05 14:49       ` Theodore Ts'o

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=20140506074455.GB29151@x2.net.home \
    --to=kzak@redhat.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).