From: Andreas Dilger <adilger@clusterfs.com>
To: Pankaj Agarwal <pankaj@pnpexports.com>
Cc: Andreas Schwab <schwab@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: how to identify filesystem type
Date: Fri, 20 Aug 2004 14:46:56 -0600 [thread overview]
Message-ID: <20040820204656.GW8967@schnapps.adilger.int> (raw)
In-Reply-To: <000901c486c9$40d92e60$6d59023d@dreammachine>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
On Aug 19, 2004 19:33 +0530, Pankaj Agarwal wrote:
>
> this is the output when you have a mounted block device.....you can only
> mount when you know the filesystem ....thats wat i wanna know...hoe to
> identify filesytems...on ablockdevice.
>
> thanks anyways, looking forward for more information on this
There is a tool available as part of e2fsprogs (1.34 maybe?) which is
called "blkid" that identifies block devices. Currently fsck uses this
to know what fsck.fstype to use, and it was my hope to have mount(8)
use this also (never got around to doing that work).
The benefits of blkid are that you can use it as a regular user, even
without read access to the disk (it will return cached values generated
by root if you don't have read access to the block device), it also will
print LABEL and UUID information to identify the filesystem, if you use
it repeatedly from some application it doesn't re-scan all of the devices
each time (important for large numbers of block devices).
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-20 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 9:07 how to identify filesystem type Pankaj Agarwal
2004-08-19 9:46 ` Andreas Schwab
2004-08-19 14:03 ` Pankaj Agarwal
2004-08-20 15:36 ` Frank Steiner
2004-08-20 20:46 ` Andreas Dilger [this message]
2004-08-20 21:58 ` Andries Brouwer
2004-08-21 3:25 ` Theodore Ts'o
2004-08-21 8:51 ` Andries Brouwer
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=20040820204656.GW8967@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj@pnpexports.com \
--cc=schwab@suse.de \
/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