[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090120184822.GF27464@shareable.org>
Date: Tue, 20 Jan 2009 18:48:22 +0000
From: Jamie Lokier <jamie@...reable.org>
To: Andreas Dilger <adilger@....com>
Cc: Coly Li <coly.li@...e.de>,
Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Roman Zippel <zippel@...ux-m68k.org>,
"Sergey S. Kostyliov" <rathamahata@...4.ru>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>,
Bob Copeland <me@...copeland.com>,
Anders Larsen <al@...rsen.net>, reiserfs-devel@...r.kernel.org,
Phillip Lougher <phillip@...gher.demon.co.uk>,
Christoph Hellwig <hch@...radead.org>,
Evgeniy Dushistov <dushistov@...l.ru>, Jan Kara <jack@...e.cz>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 0/20] return f_fsid for statfs(2)
Andreas Dilger wrote:
> On Jan 20, 2009 12:30 +0800, Coly Li wrote:
> > Ext[234] is sophisticated to have on-disk uuid record. Most file systems
> > in the patches (except jfs and reiser3) do not have a persistent uuid,
> > a reasonable/feasible solution without media format modification is fsid
> > in boot/mount life cycle. That's why huge_encode_dev(sb->s_bdev->bd_dev)
> > is used here. For jfs and reiserfs3, is there any use case for
> > persistent fsid cross boots ?
>
> I would say yes, this is worthwhile to do, or the fsid can change between
> boots unnecessarily.
Even FAT has a volume id which should probably be used.
I'm guessing NTFS does too.
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists