|
Bugzilla – Full Text Bug Listing |
| Summary: | LVM commands have gone all silent | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Neil Rickert <nwr10cst-oslnx> |
| Component: | Basesystem | Assignee: | Dong Mao Zhang <dmzhang> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | stefan.schaefer |
| Version: | 13.1 Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
The other tools like pvscan, lvscan and so on shows the same behavior in openSUSE 13.1 final. set log/silent=0 to display the pvscan normal output . or 'pvscan -v' could shows the output This is consistent with upstream. OK this strange behavior is upstream, but does it make sense? |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 After unlocking an encrypted LVM (running "cryptsetup luksOpen" at the command line: # vgscan -- gives no output # vgchange -a y -- gives no output. However, "ls /dev/mapper" shows that it apparently did make the volumes available This happens on both a 32-bit install and a 64-bit install of 13.1 Beta1 Reproducible: Always Steps to Reproduce: 1. 2. 3.