From: Oleg Drokin <green@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com,
adilger@turbolabs.com
Subject: Re: [reiserfs-dev] [PATCH] UUID & volume labels support for reiserfs
Date: Fri, 11 Jan 2002 12:23:15 +0300 [thread overview]
Message-ID: <20020111122315.B17925@namesys.com> (raw)
In-Reply-To: <20020109155504.A4551@namesys.com> <52160000.1010591279@tiny> <20020109185826.A1680@namesys.com> <100150000.1010592449@tiny> <20020109192526.A1732@namesys.com> <145590000.1010594312@tiny> <20020109194430.A2058@namesys.com> <179160000.1010596468@tiny>
In-Reply-To: <179160000.1010596468@tiny>
Hello!
On Wed, Jan 09, 2002 at 12:14:28PM -0500, Chris Mason wrote:
> > In fact, current reiserfsprogs understands these fields (look into the
> > the struct super_block definition in reiserfsprogs). It just cannot
> > change content of the fields.
> /* Structure of super block on disk */
> struct reiserfs_super_block
> {
> /* 0 */ struct reiserfs_super_block_v1 s_v1;
> /* 76 */ char sb_mnt_version[16];
> /* 92 */ char sb_mkfs_version[16];
> /*108 */ char sb_fsck_version[16];
> /*124 */ char sb_unused[204-16-16-16-SB_SIZE_V1] ;
> /* zero filled by mkreiserfs */ };
> Show me the part where it knows what a uuid is. It should at least be able
> to show the uuid set by the kernel.
It does not know about uuid per se, but it know in that area some text data is stored.
(BTW, we are started to fix reiserfsprogs, so that struct superblock will be the same in kernel and in reiserfsprogs.
It is already almost close in cvs ;) )
I see MArcello have not applied this patch to 2.4.18-pre3, so we have some more time to prepare reiserfsprogs ;)
Bye,
Oleg
prev parent reply other threads:[~2002-01-11 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 12:55 [PATCH] UUID & volume labels support for reiserfs Oleg Drokin
2002-01-09 15:47 ` [reiserfs-dev] " Chris Mason
2002-01-09 15:58 ` Oleg Drokin
2002-01-09 16:07 ` Chris Mason
2002-01-09 16:25 ` Oleg Drokin
2002-01-09 16:38 ` Chris Mason
2002-01-09 16:44 ` Oleg Drokin
2002-01-09 17:14 ` Chris Mason
2002-01-11 9:23 ` Oleg Drokin [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=20020111122315.B17925@namesys.com \
--to=green@namesys.com \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox