From: "Xuân Baldauf" <xuan--2006.08.31--reiserfs-list--namesys.com@baldauf.org>
To: reiserfs-list@namesys.com
Subject: bug: Unable to mount reiserfs from DVD+R
Date: Thu, 31 Aug 2006 01:33:57 +0200 [thread overview]
Message-ID: <44F62065.5020500@baldauf.org> (raw)
Hello,
I created backup DVDs formatted using reiserfs. However, mounting them
is not possible. If I try to mount such a DVD, I get following results:
Aug 31 01:08:18 notebook2 kernel: ReiserFS: hdc: using ordered data mode
Aug 31 01:08:18 notebook2 kernel: ReiserFS: hdc: warning: sh-458:
journal_init_dev: cannot init journal device 'unknown-block(22,0)': -30
Aug 31 01:08:18 notebook2 kernel: ReiserFS: hdc: warning: sh-462: unable
to initialize jornal device
Aug 31 01:08:18 notebook2 kernel: ReiserFS: hdc: warning: sh-2022:
reiserfs_fill_super: unable to initialize journal space
I get this error even when mounting using "-o ro,nolog".
I tracked this down to the method "journal_init_dev", which opens the
journal device with mode "blkdev_mode = FMODE_READ | FMODE_WRITE;"
except when the journal device is marked read only. However, as it
seems, my DVD burner drive is able to write DVD media (so it is not a
read-only-device, in general), but the particular DVD is only readable,
not writable. That's why (I think) the journal device itself is not
marked read only and yet "open_by_devnum(jdev, blkdev_mode);" fails.
The method "journal_init_dev" should honor the mount options "ro" or
"nolog" or both, which it currently does not (as of Linux 2.6.18-rc4).
Alternatively, method "journal_init_dev" might try to open the journal
device again (only using "read only" mode) in case the first try to open
results in -EROFS.
Xuân Baldauf.
next reply other threads:[~2006-08-30 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 23:33 Xuân Baldauf [this message]
2006-08-31 19:54 ` bug: Unable to mount reiserfs from DVD+R Hans Reiser
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=44F62065.5020500@baldauf.org \
--to=xuan--2006.08.31--reiserfs-list--namesys.com@baldauf.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 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.