From: Gord Urquhart <gordu@cray.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] No space on device message, Not true
Date: Sun, 27 Nov 2005 14:46:02 -0800 [thread overview]
Message-ID: <438A372A.3080909@cray.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Hello all
I've just install LVM2 on a SLES 9 box, that all went fine. I have
--- Logical volume ---
LV Name /dev/vg01/lvol1
VG Name vg01
LV UUID 4CyIWf-D3iO-mFZG-XiT1-xSXz-j7K2-WSZbEp
LV Write Access read/write
LV Status available
# open 2
LV Size 10.90 TB
Current LE 2857374
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:1
I have it mounted as /users and am exporting it. On another SLES9
machine I am mounting it. This all works fine. However when I try to
create multiple files on it I get messages like
/users1 # cp -r /usr/local/ .
cp: writing `./local/bin/hssdb': No space left on device
cp: closing `./local/bin/hssdb': No space left on device
cp: closing `./local/lib64/libufp.a': No space left on device
There is scads of space
/users1 # df .
Filesystem 1K-blocks Used Available Use% Mounted on
s712-5:/users1 11703708896 36960 11703671936 1% /users1
And this only happens on the nodes that NFS mount the file system. On
the local node everything works fine.
any help would be appreciated
thanks
gord u
[-- Attachment #2: gordu.vcf --]
[-- Type: text/x-vcard, Size: 254 bytes --]
begin:vcard
fn:Gord Urquhart
n:Urquhart;Gord
org:Cray Canada
adr;dom:Cell 778 229 2220 ;;Desk 604-484-3187
email;internet:gordu@cray.com
title:3rd level support XD1
tel;work:604 484 3187
tel;cell:778 229 2220
x-mozilla-html:TRUE
version:2.1
end:vcard
next reply other threads:[~2005-11-27 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 22:46 Gord Urquhart [this message]
2005-11-28 18:14 ` [linux-lvm] No space on device message, Not true Thomas Hager
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=438A372A.3080909@cray.com \
--to=gordu@cray.com \
--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.