From: Jason Walker <unseen@sover.net>
To: LVM Mailing List <linux-lvm@sistina.com>
Subject: [linux-lvm] LVM and devfs
Date: Tue, 27 Feb 2001 16:23:41 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.10.10102271621150.521-200000@surreal.localdomain> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 349 bytes --]
Hello all,
I have a few errros on boot that are generated by devfs, as much as I can
figure. it doesn't like the fact that LVM creates devices or something. I
have attacked a small file that contains the errors. Everything *works*
fine, but I still don't like seeing errors spewed on bootup. Any help
woudl be greatly appreciated. TIA!
RegEx
[-- Attachment #2: Type: TEXT/PLAIN, Size: 2107 bytes --]
Setting up LVM Volume Groups...
modprobe: Can't locate module /dev/lvm
vgscan -- reading all physical volumes (this may take a while...)
hub.c: USB new device connect on bus1/1, assigned device number 3
Manufacturer: Logitech
Product: USB Receiver
mouse0: PS/2 mouse device for input0
input0: USB HID v1.10 Mouse [Logitech USB Receiver] on usb1:3.0
modprobe: Can't locate module /dev/raid
modprobe: Can't locate module /dev/raid
vgscan -- found inactive volume group "raid"
modprobe: Can't locate module /dev/raid
modprobe: Can't locate module /dev/raid
modprobe: Can't locate module /dev/raid
modprobe: Can't locate module /dev/raid/group
modprobe: Can't locate module /dev/raid/swap
modprobe: Can't locate module /dev/raid/swap
modprobe: Can't locate module /dev/raid/tmp
modprobe: Can't locate module /dev/raid/tmp
modprobe: Can't locate module /dev/raid/mp3
modprobe: Can't locate module /dev/raid/mp3
modprobe: Can't locate module /dev/raid/anime
modprobe: Can't locate module /dev/raid/anime
modprobe: Can't locate module /dev/raid/usr
modprobe: Can't locate module /dev/raid/usr
modprobe: Can't locate module /dev/raid/home
modprobe: Can't locate module /dev/raid/home
modprobe: Can't locate module /dev/raid/var
modprobe: Can't locate module /dev/raid/var
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: you may not have an actual VGDA backup of your volume
group
devfs: devfs_register(): device already registered: "group"
vgchange -- volume group "raid" successfully activated
Checking all file systems...
Parallelizing fsck version 1.19 (13-Jul-2000)
Setting kernel variables.
Mounting local filesystems...
modprobe: Can't locate module /dev/cdroms/cdrom1
none on /proc/bus/usb type usbdevfs (rw)
Start mounting filesystem: ide0(3,5)
Ending clean XFS mount for filesystem: ide0(3,5)
/dev/ide/host0/bus0/target0/lun0/part5 on /boot type xfs (rw)
Start mounting filesystem: lvm(58,2)
Ending clean XFS mount for filesystem: lvm(58,2)
/dev/raid/mp3 on /raid/mp3 type xfs (rw)
etc,etc, everything else is fine
next reply other threads:[~2001-02-27 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 21:23 Jason Walker [this message]
2001-02-28 12:27 ` [linux-lvm] LVM and devfs Heinz J. Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2003-12-15 7:56 Stuart Felenstein
2003-12-15 11:49 ` Jord Tanner
2003-12-15 15:22 ` Stuart Felenstein
2003-12-15 13:44 ` Luca Berra
2003-12-15 15:22 ` Stuart Felenstein
2003-12-15 16:49 ` Luca Berra
2003-12-15 17:19 ` Tupshin Harper
2003-12-15 18:20 ` Frank Benkstein
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=Pine.LNX.4.10.10102271621150.521-200000@surreal.localdomain \
--to=unseen@sover.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;
as well as URLs for NNTP newsgroup(s).