Bug 218351 - creating ro lvm volumes cause "failed write" errors
Summary: creating ro lvm volumes cause "failed write" errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lvm2
Version: 4.4
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Milan Broz
QA Contact: Corey Marthaler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-04 20:11 UTC by Corey Marthaler
Modified: 2013-03-01 04:04 UTC (History)
6 users (show)

Fixed In Version: RHBA-2007-0287
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-05-08 00:13:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0287 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2007-04-28 19:01:34 UTC

Description Corey Marthaler 2006-12-04 20:11:11 UTC
Description of problem:
We should do something about failure messages when creating ro volumes. 

[root@link-08 tmp]# lvcreate -L 10G -p r corey
  /dev/corey/lvol0: write failed after 0 of 4096 at 0: Operation not permitted
  Logical volume "lvol0" created


Version-Release number of selected component (if applicable):
[root@link-08 tmp]# rpm -q lvm2
lvm2-2.02.16-1
[root@link-08 tmp]# rpm -q device-mapper
device-mapper-1.02.13-1

Comment 1 Alasdair Kergon 2006-12-06 20:26:13 UTC
For a normal LV with -Zy (the default), the code should probably activate rw,
wipe, reactivate ro.

For a snapshot, current code doesn't give the error, so likely not to need changing.

Comment 2 Milan Broz 2007-01-10 14:19:55 UTC
Fixed upstream, correct warning is printed if read only flag set.
(Same problem in lvconvert - fixed too.)

Comment 3 Corey Marthaler 2007-01-18 22:59:37 UTC
Fix verified in lvm2-2.02.19-1.el4.

[root@link-08 bin]# lvcreate -L 10G -p r vg
  WARNING: "lvol0" not zeroed
  Logical volume "lvol0" created


Comment 7 Red Hat Bugzilla 2007-05-08 00:13:48 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0287.html


Note You need to log in before you can comment on or make changes to this bug.