From: "Jason Pyeron" <jpyeron@pdinc.us>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Confusing error: No space left on device
Date: Tue, 17 Feb 2015 11:52:43 -0500 [thread overview]
Message-ID: <A3158969DA2045E5A22780BE845B20CA@black> (raw)
In-Reply-To: <848E1BB85A9C4FB5A91BC299FEB36775@black>
> -----Original Message-----
> From: Jason Pyeron
> Sent: Tuesday, February 17, 2015 11:21
>
> This is likely a problem between keyboard and chair, but it
> has got me confused all the same.
>
> I was having issues with rsync, so I switched to dd and the
> same problem persists.
>
> Any suggestions?
>
> History says "lvcreate --size 8589934592b --name
> ciphershed-dmz-http vg_five66"
>
>
> root@five-66 ~
> # dd of=/dev/vg_five66/ciphershed-dmz-http bs=512 if=/dev/zero
> dd: writing `/dev/vg_five66/ciphershed-dmz-http': No space
> left on device
> 8580489+0 records in
> 8580488+0 records out
> 4393209856 bytes (4.4 GB) copied, 11.1884 s, 393 MB/s
>
> root@five-66 ~
> # lvdisplay /dev/vg_five66/ciphershed-dmz-http
> --- Logical volume ---
> LV Path /dev/vg_five66/ciphershed-dmz-http
> LV Name ciphershed-dmz-http
> VG Name vg_five66
> LV UUID 3yQHr9-WpdJ-76eL-4lEZ-hv0X-HP3N-GgqOvN
> LV Write Access read/write
> LV Creation host, time five-66.pdinc.us, 2015-02-17 05:05:17 -0500
> LV Status available
> # open 0
> LV Size 8.00 GiB
> Current LE 2048
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 253:3
>
>
> root@five-66 ~
> # vgdisplay
> --- Volume group ---
> VG Name vg_five66
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 36
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 5
> Open LV 2
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 1.82 TiB
> PE Size 4.00 MiB
> Total PE 476806
> Alloc PE / Size 19866 / 77.60 GiB
> Free PE / Size 456940 / 1.74 TiB
> VG UUID drT68w-cRLR-ZcmV-VYFz-haaK-Djd4-S8q9EV
>
>
> root@five-66 ~
> # rpm -qf `which vgdisplay`
> lvm2-2.02.111-2.el6_6.1.x86_64
>
> root@five-66 ~
> # uname -a
> Linux five-66.pdinc.us 2.6.32-504.8.1.el6.x86_64 #1 SMP Wed
> Jan 28 21:11:36 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
# lvremove /dev/vg_five66/ciphershed-dmz-http
Do you really want to remove active logical volume ciphershed-dmz-http? [y/n]: y
Logical volume "ciphershed-dmz-http" successfully removed
root@five-66 ~
# lvcreate --size 8589934592b --name ciphershed-dmz-http vg_five66
Logical volume "ciphershed-dmz-http" created
root@five-66 ~
# dd of=/dev/vg_five66/ciphershed-dmz-http bs=512 if=/dev/zero
dd: writing `/dev/vg_five66/ciphershed-dmz-http': No space left on device
16777217+0 records in
16777216+0 records out
8589934592 bytes (8.6 GB) copied, 254.765 s, 33.7 MB/s
root@five-66 ~
# lvdisplay /dev/vg_five66/ciphershed-dmz-http
--- Logical volume ---
LV Path /dev/vg_five66/ciphershed-dmz-http
LV Name ciphershed-dmz-http
VG Name vg_five66
LV UUID slRXQ8-I3pi-2uKA-QSkd-TAwU-7deR-cKxOj9
LV Write Access read/write
LV Creation host, time five-66.pdinc.us, 2015-02-17 06:46:39 -0500
LV Status available
# open 0
LV Size 8.00 GiB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
Now I am concerned, removing and recreating fixed the issue?
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
next prev parent reply other threads:[~2015-02-17 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 16:20 [linux-lvm] Confusing error: No space left on device Jason Pyeron
2015-02-17 16:52 ` Jason Pyeron [this message]
2015-02-17 17:08 ` Jason Pyeron
2015-02-17 17:29 ` Roger Heflin
2015-02-17 19:11 ` Jason Pyeron
2015-02-17 18:53 ` Stuart Gathman
2015-02-17 20:26 ` Jason Pyeron
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=A3158969DA2045E5A22780BE845B20CA@black \
--to=jpyeron@pdinc.us \
--cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).