From: Karel Zak <kzak@redhat.com>
To: Rogier Goossens <goossens.rogier@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: libblkid fails to detect not-so-big OCFS2 filesystems
Date: Mon, 30 Jan 2012 13:26:51 +0100 [thread overview]
Message-ID: <20120130122651.GD22107@x2.net.home> (raw)
In-Reply-To: <201201271818.19325.goossens.rogier@gmail.com>
On Fri, Jan 27, 2012 at 06:18:18PM +0100, Rogier Goossens wrote:
> While testing KDE partitionmanager, I discovered that blkid did not
> detect the test OCFS2 filesystem I created. After some investigation,
> it appeared that it will assume the filesystem cannot be OCFS2 if
yes, we don't want to probe for some filesystems on very small
devices.
> smaller than 108M. However, mkfs.ocfs2 from ocfs2-tools (1.6.3) will
> happily create filesystems that are much smaller, only failing below
> approx. 15000 1k blocks, and below approx. 6000 4k blocks.
OK, fixed ... the new limit is 14000 * 1024.
Thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-01-30 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 17:18 libblkid fails to detect not-so-big OCFS2 filesystems Rogier Goossens
2012-01-30 12:26 ` Karel Zak [this message]
2012-02-07 12:01 ` Rogier Goossens
2012-02-08 10:59 ` Karel Zak
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=20120130122651.GD22107@x2.net.home \
--to=kzak@redhat.com \
--cc=goossens.rogier@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox