From: Bradley M Alexander <storm@tux.org>
To: linux-lvm@sistina.com
Subject: [linux-lvm] More research on lvm problems
Date: Sun Nov 18 23:59:02 2001 [thread overview]
Message-ID: <20011119010011.A891@sonsofthunder.yi.org> (raw)
Hi all,
I still have not gotten lvm to work as advertised. I used the old /var
partition since it would hang the machine because it could not mount the
/var partition in the volgroup.
The machine booted and I ran vgscan and vgchange -a y, and got the drive
errors prior to it finding and activating the volume group. I logged in and
tried to mount -a, and got the following:
[defiant /home/storm]# mount -a
mount: special device /dev/vg01/lvm_tmp does not exist
mount: special device /dev/vg01/lvm_home does not exist
mount: special device /dev/vg01/lvm_usrlocal does not exist
mount: special device /dev/vg01/lvm_opt does not exist
mount: special device /dev/vg01/lvm_backup does not exist
mount: special device /dev/vg01/lvm_archive does not exist
But looking in /dev:
[defiant /home/storm]# ls -l /dev/vg01
total 0
crw-r----- 1 root root 109, 0 Dec 31 1969 group
brw-r----- 1 root root 58, 0 Dec 31 1969 lv_archive
brw-r----- 1 root root 58, 6 Dec 31 1969 lv_backup
brw-r----- 1 root root 58, 3 Dec 31 1969 lv_home
brw-r----- 1 root root 58, 5 Dec 31 1969 lv_opt
brw-r----- 1 root root 58, 2 Dec 31 1969 lv_tmp
brw-r----- 1 root root 58, 4 Dec 31 1969 lv_usrlocal
brw-r----- 1 root root 58, 1 Dec 31 1969 lv_var
And finally, I can mount the filesystems individually:
[defiant /home/storm]# mount /dev/vg01/lv_usrlocal /usr/local
[defiant /home/storm]# mount /dev/vg01/lv_opt /opt
[defiant /home/storm]# mount /dev/vg01/lv_tmp /tmp
[defiant /home/storm]# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 1542188 1069696 472492 70% /
/dev/hda1 7746 3512 3834 48% /boot
/dev/hda5 1517920 768924 718156 52% /var
/dev/vg01/lv_archive 15728156 13261664 2466492 85% /archive
/dev/vg01/lv_home 1048540 877700 170840 84% /home
/dev/vg01/lv_usrlocal
1572812 965736 607076 62% /usr/local
/dev/vg01/lv_opt 511980 286836 225144 57% /opt
/dev/vg01/lv_tmp 155636 32848 122788 22% /tmp
Can anyone tell me why this is happening? The only time the drive errors
happen is when I vgscan, and not when the drive is in normal use. But why
must I manually mount the drives instead of using a mount -a (or better
yet, why can't the mount -a in the bootup make it happen)? Is it possible
that somewhere along the line, devfs is not properly registering the device
entries?
Thanks,
--
--Brad
============================================================================
Bradley M. Alexander, CISSP | Co-Chairman,
Beowulf System Admin/Security Specialist | NoVALUG/DCLUG Security SIG
Debian/GNU Linux Developer | storm@debian.org
| storm@tux.org
============================================================================
Try to look unimportant, they may be low on ammo.
--Murphy's Laws of Combat
next reply other threads:[~2001-11-18 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 23:59 Bradley M Alexander [this message]
2001-11-19 2:35 ` [linux-lvm] More research on lvm problems Markus Dobel
2001-11-19 12:50 ` Bradley M Alexander
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=20011119010011.A891@sonsofthunder.yi.org \
--to=storm@tux.org \
--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;
as well as URLs for NNTP newsgroup(s).