Back to bug 1021051
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Alasdair Kergon | 2013-10-18 21:28:28 UTC | Keywords | FutureFeature | |
| Red Hat Bugzilla | 2013-10-18 21:28:28 UTC | Doc Type | Bug Fix | Enhancement |
| Chris Pelland | 2014-01-02 12:54:00 UTC | Blocks | 1002699 | |
| Chris Pelland | 2014-01-09 19:25:49 UTC | CC | cpelland | |
| Severity | medium | high | ||
| Sean Cohen | 2014-06-11 08:48:35 UTC | CC | scohen | |
| Bronce McClain | 2014-12-04 20:20:13 UTC | CC | bmcclain | |
| Alasdair Kergon | 2014-12-05 03:15:30 UTC | Sub Component | Changing Logical Volumes (RHEL6) | |
| Target Release | 6.6 | 6.7 | ||
| Steve Almy | 2014-12-09 15:15:00 UTC | CC | salmy | |
| Allon Mureinik | 2014-12-11 08:21:43 UTC | CC | amureini | |
| Flags | needinfo?(agk) | |||
| Alasdair Kergon | 2014-12-11 14:44:20 UTC | Flags | needinfo?(agk) | |
| Corey Marthaler | 2014-12-11 15:06:05 UTC | CC | cmarthal | |
| Bronce McClain | 2014-12-11 16:10:12 UTC | Blocks | 1173188 | |
| Alasdair Kergon | 2015-02-26 18:45:39 UTC | Status | ASSIGNED | POST |
| Alasdair Kergon | 2015-02-27 13:53:24 UTC | Doc Text | If a Logical Volume is read-only and active but its metadata states that it should be writeable, you can now use 'lvchange --permission rw' to bring the active copy into line with the metadata and make it writeable. This does the same as 'lvchange --refresh' but might be more convenient. The opposite is also true, namely that 'lvchange --permission r' will now refresh an active Logical Volume that should be read-only. (The situation can arise if the configuration setting activation/read_only_volume_list is changed.) |
|
| Peter Rajnoha | 2015-03-04 15:35:16 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.117-1.el6 | |||
| errata-xmlrpc | 2015-03-04 15:48:13 UTC | Status | MODIFIED | ON_QA |
| Dean Jansa | 2015-03-06 20:08:40 UTC | QA Contact | mspqa-list | cluster-qe |
| Bronce McClain | 2015-03-11 17:57:09 UTC | Blocks | 1200970 | |
| Bronce McClain | 2015-03-11 17:58:23 UTC | Blocks | 1200970 | |
| Corey Marthaler | 2015-04-01 16:18:15 UTC | Flags | needinfo?(agk) | |
| Alasdair Kergon | 2015-04-01 16:30:23 UTC | Flags | needinfo?(agk) | |
| Corey Marthaler | 2015-04-01 22:42:37 UTC | Status | ON_QA | VERIFIED |
| Laura Bailey | 2015-06-18 00:36:47 UTC | Docs Contact | slevine | |
| Steven J. Levine | 2015-06-22 20:25:33 UTC | Doc Text | If a Logical Volume is read-only and active but its metadata states that it should be writeable, you can now use 'lvchange --permission rw' to bring the active copy into line with the metadata and make it writeable. This does the same as 'lvchange --refresh' but might be more convenient. The opposite is also true, namely that 'lvchange --permission r' will now refresh an active Logical Volume that should be read-only. (The situation can arise if the configuration setting activation/read_only_volume_list is changed.) | The lvchange -p command can now change in-kernel permissions on a logical volume. If a logical volume is read-only and active but its metadata states that it should be writeable (a situation that can arise if the configuration setting activation/read_only_volume list is changed), you can now use the "lvchange --permission rw" command to bring the active copy in line with the metadata and make it writeable. Executing an "lvchange --refresh" can do this as well, but this new feature might be more convenient in some circumstances. The opposite is also true: The "lvchange --permission r" command will now refresh an active logical volume that should be read-only. For information on the lvchange command, see the lvchange(8) man page. |
| Steven J. Levine | 2015-06-23 14:38:42 UTC | Doc Text | The lvchange -p command can now change in-kernel permissions on a logical volume. If a logical volume is read-only and active but its metadata states that it should be writeable (a situation that can arise if the configuration setting activation/read_only_volume list is changed), you can now use the "lvchange --permission rw" command to bring the active copy in line with the metadata and make it writeable. Executing an "lvchange --refresh" can do this as well, but this new feature might be more convenient in some circumstances. The opposite is also true: The "lvchange --permission r" command will now refresh an active logical volume that should be read-only. For information on the lvchange command, see the lvchange(8) man page. | The lvchange -p command can now correct in-kernel permissions on a logical volume. If a logical volume is read-only and active but its metadata states that it should be writeable (a situation that can arise if the configuration setting activation/read_only_volume list is changed), you can now use the "lvchange --permission rw" command to bring the active copy in line with the metadata and make it writeable. Executing an "lvchange --refresh" command can do this as well, but this new feature might be more convenient in some circumstances. The opposite is also true: The "lvchange --permission r" command will now refresh an active logical volume that should be read-only. For information on the lvchange command, see the lvchange(8) man page. |
| Laura Bailey | 2015-07-06 05:09:18 UTC | Doc Text | The lvchange -p command can now correct in-kernel permissions on a logical volume. If a logical volume is read-only and active but its metadata states that it should be writeable (a situation that can arise if the configuration setting activation/read_only_volume list is changed), you can now use the "lvchange --permission rw" command to bring the active copy in line with the metadata and make it writeable. Executing an "lvchange --refresh" command can do this as well, but this new feature might be more convenient in some circumstances. The opposite is also true: The "lvchange --permission r" command will now refresh an active logical volume that should be read-only. For information on the lvchange command, see the lvchange(8) man page. | lvchange -p now corrects in-kernel permissions on a logical volume If a logical volume is read-only and active but its metadata states that it should be writeable (a situation that can arise if the configuration setting activation/read_only_volume list is changed), you can now use the "lvchange --permission rw" command to bring the active copy in line with the metadata and make it writeable. Executing an "lvchange --refresh" command can do this as well, but this new feature might be more convenient in some circumstances. The opposite is also true: The "lvchange --permission r" command will now refresh an active logical volume that should be read-only. For information on the lvchange command, see the lvchange(8) man page. |
| Steven J. Levine | 2015-07-08 00:16:52 UTC | Doc Text | lvchange -p now corrects in-kernel permissions on a logical volume If a logical volume is read-only and active but its metadata states that it should be writeable (a situation that can arise if the configuration setting activation/read_only_volume list is changed), you can now use the "lvchange --permission rw" command to bring the active copy in line with the metadata and make it writeable. Executing an "lvchange --refresh" command can do this as well, but this new feature might be more convenient in some circumstances. The opposite is also true: The "lvchange --permission r" command will now refresh an active logical volume that should be read-only. For information on the lvchange command, see the lvchange(8) man page. | lvchange -p now corrects in-kernel permissions on a logical volume If a logical volume is read-only and active but its metadata states that it should be writeable (a situation that can arise if the configuration setting activation/read_only_volume_list is changed), you can now use the "lvchange --permission rw" command to bring the active copy in line with the metadata and make it writeable. Executing an "lvchange --refresh" command can do this as well, but this new feature might be more convenient in some circumstances. The opposite is also true: The "lvchange --permission r" command will now refresh an active logical volume that should be read-only. For information on the lvchange command, see the lvchange(8) man page. |
| errata-xmlrpc | 2015-07-22 07:37:02 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2015-07-22 03:37:02 UTC |
Back to bug 1021051