From: Ed Tomlinson <tomlins@cam.org>
To: linux-lvm@sistina.com, Chris Mason <mason@suse.com>
Subject: Re: [linux-lvm] mounting reiserfs snapshot fails
Date: Fri, 13 Apr 2001 18:42:19 -0400 [thread overview]
Message-ID: <01041318421900.14209@oscar> (raw)
In-Reply-To: <363990000.987194192@tiny>
On Friday 13 April 2001 16:36, Chris Mason wrote:
> On Friday, April 13, 2001 01:29:58 PM -0400 Ed Tomlinson <tomlins@cam.org>
>
> wrote:
> > Hi,
> >
> > Using debian sid, 2.4.3-ac5, lvm 0.91 beta7, with the vfs locking
> > patch applied I get:
> >
> > oscar# mount /dev/lv/snap /snap -t reiserfs -oro
> > mount: wrong fs type, bad option, bad superblock on /dev/lv/snap,
> > or too many mounted file systems
>
> BTW, you can drop the -o ro, LVM sets the snapshot device readonly, so VFS
> forces a readonly mount for you.
>
> > When trying to mount the snap shot. It was created with:
> > lvcreate -L 1G -s -n snap /dev/lv/root /dev/hdg1
> > without problems
>
> I doubt it, but was /dev/lv/root a freshly created reiserfs disk?
>
> What does dumpreiserfs tell you about /dev/lv/snap and /dev/lv/root tell
> you?
oscar# lvcreate -L 1G -s -n snap /dev/lv/root /dev/hdg1
lvcreate -- WARNING: the snapshot will be automatically disabled once it gets full
lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/lv/snap"
lvcreate -- doing automatic backup of "lv"
lvcreate -- logical volume "/dev/lv/snap" successfully created
oscar# mount -t reiserfs /dev/lv/snap /snap
mount: block device /dev/lv/snap is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/lv/snap,
or too many mounted file systems
oscar# dumpreiserfs /dev/lv/snap
dumpe2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
dumpreiserfs: Bad magic number in super-block while trying to open /dev/lv/snap
Couldn't find valid filesystem superblock.
oscar# dumpreiserfs /dev/lv/root
dumpe2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
dumpreiserfs: Bad magic number in super-block while trying to open /dev/lv/root
Couldn't find valid filesystem superblock.oscar# debugreiserfs /dev/lv/snap
<-------------debugreiserfs, 2001------------->
reiserfsprogs 3.x.0j
reiserfs_open: neither new nor old reiserfs format found on /dev/lv/snap
print_block: buffer is NULL
oscar# debugreiserfs /dev/lv/root
<-------------debugreiserfs, 2001------------->
reiserfsprogs 3.x.0j
Super block of format 3.6 found on the 0x3 in block 16
Block count 3670016
Blocksize 4096
Free blocks 1241068
Busy blocks (skipped 16, bitmaps - 112, journal blocks - 8193
1 super blocks, 2420626 data blocks
Root block 40201
Journal block (first) 18
Journal dev 0
Journal orig size 8192
Filesystem state ERROR
Tree height 5
Hash function used to sort names: "r5"
Objectid map size 304, max 972
Version 2
oscar# = ?
Ed
next prev parent reply other threads:[~2001-04-13 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 17:29 [linux-lvm] mounting reiserfs snapshot fails Ed Tomlinson
2001-04-13 20:36 ` Chris Mason
2001-04-13 22:42 ` Ed Tomlinson [this message]
2001-04-14 0:23 ` Andreas Dilger
2001-04-14 0:53 ` [reiserfs-list] " Chris Mason
2001-04-18 1:38 ` Ed Tomlinson
2001-04-30 1:48 ` [linux-lvm] Re: [reiserfs-list] " Chris Mason
2001-04-30 4:23 ` Ed Tomlinson
2001-04-30 4:31 ` Ed Tomlinson
2001-04-30 11:43 ` Chris Mason
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=01041318421900.14209@oscar \
--to=tomlins@cam.org \
--cc=linux-lvm@sistina.com \
--cc=mason@suse.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;
as well as URLs for NNTP newsgroup(s).