From: Davidlohr Bueso <dave@gnu.org>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] allow to create a minix3fs with a blocksize != 1K
Date: Mon, 11 Jun 2012 13:45:04 +0200 [thread overview]
Message-ID: <1339415104.2684.10.camel@offbook> (raw)
In-Reply-To: <4FD501AE.2070506@gmail.com>
On Sun, 2012-06-10 at 22:21 +0200, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> On 10.06.2012 21:58, Davidlohr Bueso wrote:
>
> > On Wed, 2012-05-09 at 23:56 +0200, Vladimir 'φ-coder/phcoder' Serbinenko
> > wrote:
> >> Have used it to test minixfs support with various block sizes.
> >>
> >
> > Hi Vladimir,
> >
> > A few comments:
> >
> > + if (MINIX_BLOCK_SIZE % 512 || MINIX_BLOCK_SIZE < 1024
> > + || MINIX_BLOCK_SIZE >= 65536)
> > + usage();
> >
> > This check should be part of the switch statement, perhaps in its own
> > function.
> > + if (*tmp && ...)
> >
> >
>
> Ok
>
> > + if (fs_version != 3 && MINIX_BLOCK_SIZE != MINIX12_BLOCK_SIZE)
> > + usage();
> >
> > We should set -1/-2 options to be mutually exclusive with -B.
> >
>
> Ok
>
> > +#define MAX_MINIX_BLOCK_SIZE 65536
> > Isn't the max minix block size 4096?
> >
>
> No, Maximum for the on-disk format is 65535. Minix itself supports
> everything from 1025 to 65536-512 as long as it's divisible by 512.
> Linux driver is limited to 1024, 2048 and 4096
hmmm, do you have any documentation I can look at? Both the native mkfs
minix tool and the mfs server, also set the max block size to 4K.
Unfortunately I don't have a copy of ast's minix book.
>
> > +#define MINIX12_BLOCK_SIZE 1024
> > This is the minimal block size, including v3. MINIX12_ doesn't describe
> > it well.
> >
>
> I use this constant specifically in places which only relate to v1 and v2
>
> >
> > Also, please send the patches in the body of the message - just as with
> > the lkml.
> >
>
> Ok
>
> > Thanks,
> > Davidlohr
> >
> >
>
>
>
next prev parent reply other threads:[~2012-06-11 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 21:51 [PATCH] allow to create a minix3fs with a blocksize != 1K Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-09 21:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-15 9:05 ` Karel Zak
2012-06-10 19:58 ` Davidlohr Bueso
2012-06-10 20:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-06-11 11:45 ` Davidlohr Bueso [this message]
2012-05-09 21:57 ` richard -rw- weinberger
2012-05-09 22:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-09 22:08 ` richard -rw- weinberger
2012-05-09 22:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=1339415104.2684.10.camel@offbook \
--to=dave@gnu.org \
--cc=kzak@redhat.com \
--cc=phcoder@gmail.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 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.