mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Torrey Hoffman <thoffman@arnor.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
	Reiserfs List <reiserfs-list@namesys.com>
Subject: Mounting reiserfs with nonstandard journal size fails
Date: 29 Oct 2002 15:36:20 -0800	[thread overview]
Message-ID: <1035934581.1487.1409.camel@rivendell.arnor.net> (raw)

I'm having trouble mounting a reiserfs filesystem created with a
nonstandard (smaller) journal size.  But if I use the default journal
size, it works fine.

The filesystem is on a 64 MB compact flash attached to a USB reader. It
has a single partition, which appears as /dev/sda1.

I've done a little detective work with strace'ing mount (8). It calls
mount (2) which fails with EINVAL, which seems to indicate a bad
superblock in this case.  It appears that the in-kernel superblock
parsing for reiserfs does not understand non-standard journal sizes.

My kernel is an updated Red Hat 7.3 (2.4.18-10) and my reiserfsprogs are
3.6.3, downloaded from www.namesys.com and compiled locally.  My mount
program is version 2.11n, the standard Red Hat version.

Is this fixed in later kernels?

Another strange thing I noticed: if I strace a successful mount of the
normal reiserfs, I see two calls to mount (2) in the output.  The first
returns ENOSYS, which is not documented on the mount(2) manpage, but the
second identical call succeeds.  Weird.  Time to have a look at the
mount sourcecode I guess...

successful mount strace output:
...
mount("/dev/sda1", "/mnt/flash", "reiserfs", 0xc0ed0000, 0) = -1 ENOSYS
(Function not implemented)
mount("/dev/sda1", "/mnt/flash", "reiserfs", 0xc0ed0000, 0) = 0
...

Torrey Hoffman
thoffman@arnor.net
torrey.hoffman@myrio.com






             reply	other threads:[~2002-10-29 23:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 23:36 Torrey Hoffman [this message]
2002-10-30  6:39 ` [reiserfs-list] " Oleg Drokin
2002-10-30 21:29   ` Hans Reiser
2002-10-31  5:43     ` Oleg Drokin

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=1035934581.1487.1409.camel@rivendell.arnor.net \
    --to=thoffman@arnor.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@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

all inboxes | Powered by JetHome®