From: Clifford Beshers <clifford.beshers@lindows.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Reiserfs mail-list <Reiserfs-List@namesys.com>,
Vitaly Fertman <vitaly@namesys.com>
Subject: Re: 2 Terabyte install
Date: Wed, 12 May 2004 16:22:56 -0700 [thread overview]
Message-ID: <40A2B1D0.5040005@lindows.com> (raw)
In-Reply-To: <20040512034150.GS9641@schnapps.adilger.int>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Andreas Dilger wrote:
>> * Is there a tool to determine the type of file system on a
>> partition without mounting it?
>>
>>
>
>Lots of them. "file -s /dev/foo" or if you have a newer e2fsprogs (1.33
>and newer I think) you can use "blkid [dev ...]" to tell you a bunch of
>things about each device (LABEL, UUID, TYPE).
>
>
>
>
Very interesting. Unfotunately, my results don't match yours.
First, I had tried 'file' and found that it didn't work. I tried it
again and found that it still didn't work.
root@notsomarlin:~# losetup /dev/loop/0 /tmp/foo
root@notsomarlin:~# mke2fs /dev/loop/0
...
root@notsomarlin:~# file /tmp/foo
/tmp/foo: Linux rev 1.0 ext2 filesystem data
root@notsomarlin:~# mkreiserfs /dev/loop/0
...
ReiserFS is successfully created on /dev/loop/0.
root@notsomarlin:~# file /tmp/foo
/tmp/foo: data
Do you get other results? If not, it would seem that Debian's version
of 'file' is broken, yet I checked the source code and there are magic
numbers for reiserfs included.
Also, I check e2fsprogs and it is at version 1.35 in Debian unstable,
but no tool called 'blkid' is included.
So I'm still searching for reliable methods to do this.
[-- Attachment #2: Type: text/html, Size: 1699 bytes --]
next prev parent reply other threads:[~2004-05-12 23:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 22:58 2 Terabyte install Clifford Beshers
2004-05-07 8:18 ` Vladimir Saveliev
2004-05-07 16:17 ` Hans Reiser
2004-05-07 16:48 ` Clifford Beshers
2004-05-07 17:38 ` Lamont R. Peterson
2004-05-10 16:53 ` Hans Reiser
2004-05-11 15:23 ` Vladimir Karavelov
2004-05-12 2:51 ` Clifford Beshers
2004-05-12 3:41 ` Andreas Dilger
2004-05-12 6:51 ` Vladimir Saveliev
2004-05-12 7:06 ` Philippe Gramoullé
2004-05-12 23:22 ` Clifford Beshers [this message]
2004-05-12 23:36 ` Clifford Beshers
2004-05-12 16:59 ` Hans Reiser
2004-05-12 18:24 ` Mike Benoit
2004-05-12 18:36 ` Chris Mason
2004-05-12 18:30 ` Clifford Beshers
2004-05-13 5:43 ` Hans Reiser
2004-05-13 20:04 ` Paul Wagland
2004-05-13 20:11 ` mjt
2004-05-16 17:07 ` Namesys now accepts Visa cards on our website (support questions and donations both) Hans Reiser
2004-05-16 17:22 ` mjt
2004-05-16 17:43 ` Hans Reiser
2004-05-17 8:24 ` Domenico Andreoli
2004-05-20 18:22 ` Redeeman
2004-05-20 18:37 ` mjt
2004-05-20 18:55 ` Redeeman
2004-05-15 21:28 ` 2 Terabyte install Hans Reiser
2004-05-20 18:24 ` Redeeman
2004-05-07 17:44 ` Lamont R. Peterson
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=40A2B1D0.5040005@lindows.com \
--to=clifford.beshers@lindows.com \
--cc=Reiserfs-List@namesys.com \
--cc=adilger@clusterfs.com \
--cc=vitaly@namesys.com \
/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.