From: "Linda A. Walsh" <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Bug! lvs shouldn't need 'root' access
Date: Sun, 10 Jul 2011 10:40:13 -0700 [thread overview]
Message-ID: <4E19E3FD.9000805@tlinx.org> (raw)
When I do an lvs to look at he sizes of my devs, I get:
lvm> lvs
WARNING: Running as a non-root user. Functionality may be unavailable.
/dev/ram0: open failed: Operation not permitted
/dev/dm-0: open failed: Operation not permitted
/dev/ram1: open failed: Operation not permitted
/dev/sda1: open failed: Operation not permitted
/dev/dm-1: open failed: Operation not permitted
/dev/ram2: open failed: Operation not permitted
....
/dev/ram16: open failed: Operation not permitted
/dev/ram17: open failed: Operation not permitted
...
/dev/sdb1: open failed: Operation not permitted
/dev/sdc6: open failed: Operation not permitted
...
No volume groups found.
Thing is, ll '/dev/sd?' show:
brw-rw---- 1 root disk 8, 0 Jul 8 23:52 /dev/sda
brw-rw---- 1 root disk 8, 16 Jul 8 23:52 /dev/sdb
brw-rw---- 1 root disk 8, 32 Jul 8 16:52 /dev/sdc
brw-rw---- 1 root disk 8, 48 Jul 8 16:52 /dev/sdd
and me:
> groups
tty disk mail wheel games audio SYSGROUP www squid trusted named
ldap backup unix_users home private powerd ....
Notice 'disk'....
and notice how group disk has same perms has uid 'root'??
I could write to the darn things!, but all I NEED is read (hmmm
maybe I should change the perms on those devs to 640, but besides
the point)....I should be able to read them! (any WHY is lvm
looking at all the ram disks? Do that many people use lvm with
ram disks? (possible, but don't see it as very useful).
So what's going on? are all the user's associated groups being
dumped somewere?
Shouldn't have to become root just to get status of things (like
running 'top', etc...)
next reply other threads:[~2011-07-10 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 17:40 Linda A. Walsh [this message]
2011-07-10 22:08 ` [linux-lvm] Bug! lvs shouldn't need 'root' access Alasdair G Kergon
2011-07-11 1:24 ` Linda A. Walsh
2011-07-11 2:24 ` Alasdair G Kergon
2011-07-11 2:31 ` Linda A. Walsh
2011-07-11 2:53 ` Alasdair G Kergon
2011-07-12 10:58 ` Linda A. Walsh
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=4E19E3FD.9000805@tlinx.org \
--to=lvm@tlinx.org \
--cc=linux-lvm@redhat.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).