From: R Dicaire <rdicaire@kritek.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] problems mounting snapshots
Date: Mon Jan 26 15:09:01 2004 [thread overview]
Message-ID: <1075147677.15213.44.camel@ws.rdb.linux-help.org> (raw)
First the specs:
Linux kernel 2.4.23-xfs patched with LVM 1.0.8
lvm tools 1.0.8
Slackware 9.1
gcc -v
Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs
Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-checking
--with-gnu-ld --verbose --target=i486-slackware-linux
--host=i486-slackware-linux
Thread model: posix
gcc version 3.2.3
The problem:
Various errors trying to mount snapshots using ext3/xfs/reiserfs
xfs:
mount -t xfs /dev/vg0/snap_home /mnt/hd -o ro
mount: wrong fs type, bad option, bad superblock on /dev/vg0/snap_home,
or too many mounted file systems
Jan 26 14:50:26 rdb kernel: XFS: Filesystem lvm(58,8) has duplicate UUID
- can't mount
ext3:
mount -t ext3 /dev/vg0/snap_tmp /mnt/hd -o ro
mount: wrong fs type, bad option, bad superblock on /dev/vg0/snap_tmp,
or too many mounted file systems
Jan 26 15:00:59 rdb kernel: EXT3-fs: INFO: recovery required on readonly
filesystem.
Jan 26 15:00:59 rdb kernel: EXT3-fs: write access unavailable, cannot
proceed.
reiserfs:
It'll mount but complains:
Jan 26 15:03:09 rdb kernel: reiserfs: found format "3.6" with standard
journal
Jan 26 15:03:09 rdb kernel: reiserfs: checking transaction log (device
lvm(58,8)) ...
Jan 26 15:03:09 rdb kernel: for (lvm(58,8))
Jan 26 15:03:09 rdb kernel: Can't write to read-only device 3a:08
Jan 26 15:03:09 rdb last message repeated 6 times
Jan 26 15:03:09 rdb kernel: reiserfs: replayed 3 transactions in 0
seconds
Jan 26 15:03:09 rdb kernel: lvm(58,8):Using tea hash to sort names
------------------------------------------------------------------
I uograded to 1.0.8 to try and fix this mount issue, to no avail.
Have I missed something? Any help would be greatly appreciated, thanks.
--
aRDy Music
http://www.ardynet.com
reply other threads:[~2004-01-26 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1075147677.15213.44.camel@ws.rdb.linux-help.org \
--to=rdicaire@kritek.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox