On 10/10/2014 07:06 PM, jd1008 issued this missive:
>
> On 10/10/2014 04:21 PM, Rick Stevens wrote:
>> On 10/10/2014 12:32 PM, jd1008 issued this missive:
>>> On 10/08/2014 03:16 AM, Ed Greshko wrote:
On 10/08/14 11:37, jd1008 wrote:
> On 10/07/2014 09:11 PM, Ed Greshko wrote:
>> lvm
On 10/10/2014 04:21 PM, Rick Stevens wrote:
On 10/10/2014 12:32 PM, jd1008 issued this missive:
On 10/08/2014 03:16 AM, Ed Greshko wrote:
On 10/08/14 11:37, jd1008 wrote:
On 10/07/2014 09:11 PM, Ed Greshko wrote:
lvm pvdisplay
lvm vgdisplay
lvm lvdisplay
# lvm pvdisplay
# lvm pvdisplay -v
On 10/10/2014 04:21 PM, Rick Stevens wrote:
On 10/10/2014 12:32 PM, jd1008 issued this missive:
On 10/08/2014 03:16 AM, Ed Greshko wrote:
On 10/08/14 11:37, jd1008 wrote:
On 10/07/2014 09:11 PM, Ed Greshko wrote:
lvm pvdisplay
lvm vgdisplay
lvm lvdisplay
# lvm pvdisplay
# lvm pvdisplay -v
On 10/10/2014 12:32 PM, jd1008 issued this missive:
>
> On 10/08/2014 03:16 AM, Ed Greshko wrote:
>> On 10/08/14 11:37, jd1008 wrote:
>>> On 10/07/2014 09:11 PM, Ed Greshko wrote:
lvm pvdisplay
lvm vgdisplay
lvm lvdisplay
>>> # lvm pvdisplay
>>> # lvm pvdisplay -v
>>> Scanning
On 10/08/2014 03:16 AM, Ed Greshko wrote:
On 10/08/14 11:37, jd1008 wrote:
On 10/07/2014 09:11 PM, Ed Greshko wrote:
lvm pvdisplay
lvm vgdisplay
lvm lvdisplay
# lvm pvdisplay
# lvm pvdisplay -v
Scanning for physical volume names
# lvm pvdisplay -vvv
Setting activation/monitoring t
What does 'ls -l /dev/sd*' say?
Have you tried 'tune2fs -l /dev/sdc3' (if there is one)? That should give you
the UUID.
Bill
On 10/8/2014 8:00 PM, Junk wrote:
Well if it's not lvm that leaves raid, luks encrypted partitions, docker or using an ssd as a cache for a magnetic
disk. dm-raid, dm
On 8 October 2014 04:37:19 GMT+01:00, jd1008 wrote:
>
>On 10/07/2014 09:11 PM, Ed Greshko wrote:
>> lvm pvdisplay
>> lvm vgdisplay
>> lvm lvdisplay
># lvm pvdisplay
># lvm pvdisplay -v
> Scanning for physical volume names
># lvm pvdisplay -vvv
> Setting activation/monitoring to 1
>
On Tue, 2014-10-07 at 21:02 -0600, jd1008 wrote:
> The funny thing about it is the amazing silence of
> the fedora devs (who also read this list), about this problem :)
AFAIK the devs tend to read the Test list and many don't read the Users
list. That said, take this to the Test list only if it a
On 10/08/14 11:37, jd1008 wrote:
>
> On 10/07/2014 09:11 PM, Ed Greshko wrote:
>> lvm pvdisplay
>> lvm vgdisplay
>> lvm lvdisplay
> # lvm pvdisplay
> # lvm pvdisplay -v
> Scanning for physical volume names
> # lvm pvdisplay -vvv
> Setting activation/monitoring to 1
> Processing: p
On 10/07/2014 09:11 PM, Ed Greshko wrote:
lvm pvdisplay
lvm vgdisplay
lvm lvdisplay
# lvm pvdisplay
# lvm pvdisplay -v
Scanning for physical volume names
# lvm pvdisplay -vvv
Setting activation/monitoring to 1
Processing: pvdisplay -vvv
O_DIRECT will be used
Sett
On 10/08/14 07:23, Junk wrote:
> What's the output of lsblk?
>
> It looks a bit like your using LVM
Actually, I'd be more interested in the output of
lvm pvdisplay
lvm vgdisplay
lvm lvdisplay
--
If you can't laugh at yourself, others will gladly oblige.
--
users mailing list
users@lists.fedo
On 10/07/2014 08:25 PM, Ralf Corsepius wrote:
On 10/07/2014 10:52 PM, jd1008 wrote:
and I try
# mount /dev/sdc3 /sdc3
mount: special device /dev/sdc3 does not exist
Well, you'd have to manually create a directory /sdc3 (The "mount
point") before mounting to make this work.
# grep sdc3 /e
On 10/07/2014 10:52 PM, jd1008 wrote:
and I try
# mount /dev/sdc3 /sdc3
mount: special device /dev/sdc3 does not exist
Well, you'd have to manually create a directory /sdc3 (The "mount
point") before mounting to make this work.
# grep sdc3 /etc/fstab
UUID=e64d7b94-1ffb-4a2e-ae59-5f8e54b6c
On 10/07/2014 05:23 PM, Junk wrote:
On 7 October 2014 21:52:05 GMT+01:00, jd1008 wrote:
# mount | grep sdc3
/dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF3 on /sdc3 type ext4
(rw,relatime,journal_checksum)
So, how come I do not see it listed as I see /dev/sda3. To wit:
# mount | grep sda3
/d
On 10/07/2014 05:23 PM, Junk wrote:
On 7 October 2014 21:52:05 GMT+01:00, jd1008 wrote:
# mount | grep sdc3
/dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF3 on /sdc3 type ext4
(rw,relatime,journal_checksum)
So, how come I do not see it listed as I see /dev/sda3. To wit:
# mount | grep sda3
/d
On 7 October 2014 21:52:05 GMT+01:00, jd1008 wrote:
># mount | grep sdc3
>/dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF3 on /sdc3 type ext4
>(rw,relatime,journal_checksum)
>
>So, how come I do not see it listed as I see /dev/sda3. To wit:
># mount | grep sda3
>/dev/sda3 on / type ext4 (rw,relat
# mount | grep sdc3
/dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF3 on /sdc3 type ext4
(rw,relatime,journal_checksum)
So, how come I do not see it listed as I see /dev/sda3. To wit:
# mount | grep sda3
/dev/sda3 on / type ext4 (rw,relatime,data=ordered)
If I unmount /dev/mapper/HGST_HTS721010
17 matches
Mail list logo
