All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Gathman <stuart@gathman.org>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Confusing error: No space left on device
Date: Tue, 17 Feb 2015 13:53:44 -0500	[thread overview]
Message-ID: <54E38E38.6040506@gathman.org> (raw)
In-Reply-To: <848E1BB85A9C4FB5A91BC299FEB36775@black>

On 02/17/2015 11:20 AM, Jason Pyeron wrote:
> 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
"No space left on device" is a filesystem error.   This happens to me 
occasionally when the /dev/... path does not actually exist for various 
reasons, and the output is going into the root filesystem instead.

In your case, the "varying reason" is rsync.  Rsync removes 
/dev/vg_five66/ciphershed-dmz-http, and creates a regular file - which 
it proceeds to fill with data from your source lv until running out of 
space in your root fs.  When you removed and recreated the LV, this 
removed the rsync handiwork and your subsequent dd worked again.  But 
when you ran rsync again - bye bye link to LV device node.

There is a patch to rsync for copying devices nodes - but the /dev/... 
pathnames are often symlinks.
There are utilities for copying block devices with rsync protocol - I 
have a python script that I have used around somewhere, but I can't put 
my fingers on it at the moment.

  parent reply	other threads:[~2015-02-17 18:53 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
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 [this message]
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=54E38E38.6040506@gathman.org \
    --to=stuart@gathman.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.