[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] Re: [catch22] lvm vs reiserfs



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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]