From: Karel Zak <kzak@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: ReFS
Date: Tue, 14 May 2013 15:42:21 +0200 [thread overview]
Message-ID: <20130514134221.GA7509@x2.net.home> (raw)
In-Reply-To: <20130514110316.GA17246@redhat.com>
On Tue, May 14, 2013 at 12:03:16PM +0100, Richard W.M. Jones wrote:
> ReFS is Microsoft's new filesystem used in Windows 2012 Server and
> above. There's no support for this in Linux (although I'm hoping to
> change that) but it'd be nice if blkid could at least recognize it.
>
> So I thought you might be interested in the filesystem signature for
> ReFS, which appears to be in the first 8 bytes:
It seems like NTFS where is
struct ntfs_super_block {
uint8_t jump[3];
uint8_t oem_id[8]; /* magic string */
and the magic string is "NTFS ".
> 00000000 00 00 00 52 65 46 53 00 00 00 00 00 00 00 00 00 |...ReFS.........|
> 00000010 46 53 52 53 00 02 c8 6b 00 00 4e 01 00 00 00 00 |FSRS...k..N.....|
> 00000020 00 02 00 00 80 00 00 00 01 01 00 00 00 00 00 00 |................|
> 00000030 00 00 00 00 00 00 00 00 95 0a d9 2c 1b d9 2c 02 |...........,..,.|
> 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
>
> There is nothing else that looks even vaguely like a superblock within
> the first few megabytes, so I'd go with those first 8 bytes for now.
The question is where is UUID and LABEL :-)
BTW, I found:
http://www.williballenthin.com/forensics/refs/
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2013-05-14 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 11:03 ReFS Richard W.M. Jones
2013-05-14 11:47 ` ReFS Richard W.M. Jones
2013-05-14 13:27 ` ReFS Richard W.M. Jones
2013-05-14 13:56 ` ReFS Karel Zak
2013-05-14 14:06 ` ReFS Richard W.M. Jones
2013-05-14 13:42 ` Karel Zak [this message]
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=20130514134221.GA7509@x2.net.home \
--to=kzak@redhat.com \
--cc=rjones@redhat.com \
--cc=util-linux@vger.kernel.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