From: josv@osp.nl
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [catch22] lvm vs reiserfs
Date: Fri, 23 Mar 2001 09:51:33 +0100 [thread overview]
Message-ID: <20010323095133.C5617@gatekeeper.osp.nl> (raw)
In-Reply-To: <20010323091953.B10727@colombina.comedia.it>
Snapshots are by their very nature read-only animals. Their internal
organisation is such that they can not easily be written to.
Mounting it readonly informs the file system of this fact.
It seems from the output that the ReiserFS code wants to replay
the journal, which leads me to believe that the file system was
not properly sync'ed before the snapshot was taken. Maybe the
VFS_lock patch needs to be updated?
++Jos
On Fri, Mar 23, 2001 at 09:19:53AM +0100, Luca Berra wrote:
> On Thu, Mar 22, 2001 at 11:33:26PM -0500, Ed Tomlinson wrote:
> > oscar# mount /dev/lv/snap /snap -treiserfs -oro
> why readonly?
>
> > reiserfs: checking transaction log (device 3a:04) ...
> > clm-2076: device is readonly, unable to replay log
> > Replay Failure, unable to mount
> > reiserfs_read_super: unable to initialize journal space
> > mount: wrong fs type, bad option, bad superblock on /dev/lv/snap,
> > or too many mounted file systems
>
> --
> Luca Berra -- bluca@comedia.it
> Communication Media & Services S.r.l.
> /"\
> \ / ASCII RIBBON CAMPAIGN
> X AGAINST HTML MAIL
> / \
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
next prev parent reply other threads:[~2001-03-23 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 19:46 [linux-lvm] [catch22] lvm vs reiserfs Ed Tomlinson
2001-03-22 20:10 ` Chris Mason
2001-03-22 21:06 ` Ed Tomlinson
2001-03-23 4:33 ` [linux-lvm] " Ed Tomlinson
2001-03-23 8:19 ` Luca Berra
2001-03-23 8:51 ` josv [this message]
2001-03-23 13:10 ` Ed Tomlinson
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=20010323095133.C5617@gatekeeper.osp.nl \
--to=josv@osp.nl \
--cc=linux-lvm@sistina.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.