From: "Tren Blackburn" <tren@eotnetworks.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Operation Not Permitted on 2.4.20
Date: Thu Dec 19 11:06:02 2002 [thread overview]
Message-ID: <007501c2a781$32784dc0$0201a8c0@fileserver> (raw)
Hi all;
I've done some searching on the list and the closest I can come up with
is this:
http://lists.sistina.com/pipermail/lvm-devel/2002-March/000873.html
This is a new NetFinity server, hardware RAID 5 array. I partitioned
the drive, set up a second partition as Linux LVM. Linux kernel is
2.4.20 and LVM version is 1.1-rc2 (kernel patched with this as well)
Ran pvcreate which worked fine
Ran vgcreate which worked fine
Ran lvcreate -L1G -nlvusr rootvg which gave:
lvcreate -- ERROR "Operation not permitted" opening logical volume
"/dev/rootvg/lvusr"
Running lvremove /dev/rootvg/lvusr gives:
lvremove -- ERROR "lv_release(): LV number" releasing logical volume
"/dev/rootvg/lvusr"
And if I try to build a filesystem on this LV I get:
count_blocks: open failed (Operation not permitted)
If I run vgscan -f I can remove the lv properly, but I cannot create a
filesystem still (get same error) What can I give in the way of debug
output to be helpful here. Is anyone else experiencing this problem?
Regards,
Tren
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- Tren Blackburn - Owner mailto:tren@eotnetworks.com =
= EOT Networks http://www.eotnetworks.com -
- Phone (403) 818-7658 Fax (403) 269-2122 =
= ** Infinite Solutions for a Finite World ** -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
------------------------------------------------------------------------
DISCLAIMER: This e-mail message is intended only for the named
recipient(s) above and may contain information that is privileged,
confidential and/or exempt from disclosure under applicable law. If you
have received this message in error, or are not the named recipient(s),
please immediately notify the sender and delete this e-mail message.
------------------------------------------------------------------------
reply other threads:[~2002-12-19 11:06 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='007501c2a781$32784dc0$0201a8c0@fileserver' \
--to=tren@eotnetworks.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.