From: "Måns Rullgård" <mru@kth.se>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Re: LVM2 + Linux 2.6.1 questions
Date: Mon Jan 26 10:44:02 2004 [thread overview]
Message-ID: <yw1xektm3edc.fsf@ford.guide> (raw)
In-Reply-To: web-216233373@mail01.infosat.net
"Dale Gallagher" <foobar@mighty.co.za> writes:
> Hi there
>
> I've successfully setup LVM2.2.00.08 and
> device-mapper.1.00.07 on a Slackware 9.1 host with Linux
> 2.6.1. I have a question or two:
>
> 1) Would a shutdown error something like the following, be
> attributed to LVM and/or device-mapper?
>
> /proc/devices: fopen failed - no such file or directory
It's probably caused by LVM. I see them too. Everything works
anyway, so I don't care that much.
> 2) Why do I see, for example, a /dev/mapper/v01-home entry,
> instead of /dev/v01/home, when running 'df' and 'mount'? I
> see that /dev/mapper/v01/home symlinks to
> /dev/mapper/v01-home, which must account for this, though I
> thought that because I'd specified /dev/v01/home, that it'd
> appear as such? Not that this really matters I suppose ;-)
I see the /dev/vg/link name.
> $ df -h | grep v01
> /dev/mapper/v01-home 2.9G 444M 2.4G 16% /home
> /dev/mapper/v01-usr 2.0G 1.1G 760M 60% /usr
> /dev/mapper/v01-var 985M 30M 906M 4% /var
>
> $ mount | grep v01
> /dev/mapper/v01-home on /home type ext3 (rw)
> /dev/mapper/v01-usr on /usr type ext3 (rw)
> /dev/mapper/v01-var on /var type ext3 (rw)
>
> 3) Does anyone know when LVM2 specific docs, such as a
> HOWTO and FAQ will be available?
It doesn't seem like you need one, if you've gotten this far.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-01-26 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 10:06 [linux-lvm] LVM2 + Linux 2.6.1 questions Dale Gallagher
2004-01-26 10:44 ` Måns Rullgård [this message]
2004-01-27 0:14 ` [linux-lvm] " Navindra Umanee
2004-01-27 2:15 ` Dale Gallagher
2004-01-27 3:17 ` Måns Rullgård
2004-01-27 18:45 ` Navindra Umanee
2004-01-28 10:45 ` [linux-lvm] " AJ Lewis
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=yw1xektm3edc.fsf@ford.guide \
--to=mru@kth.se \
--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