Displaying 3 results from an estimated 3 matches for "29gb".
Did you mean:
20gb
2004 Apr 12
3
cp -al issues
...he bulk of
the 37GB, should this happen? Shouldn't /Current always have the actual
copy (37Gb)?
Here is the results of du from the last two days. The first day it seems
normal because there was about 1.4Gb of changes, but on the second day
4-8-2004 now has changed to 9.1Gb and Current is only 29Gb?? Strange.
Does this mean that 4-8-2004 is no longer properly hard-linked to
/Current?
Would there be any difference using --link-destination in rsync and not
using cp at all?
[root@gfi backup]# du --max-depth=1 -h
37G ./Current
1.4G ./04-08-2004
26M ./04-09-2004
38G .
[root@gfi...
2011 May 27
3
Rsync "file too large (27)"
Hi,
I'm getting the following error occasional and can't find out why;
05/14/2011 09:28:51 rsyncing /dbtmp to /dbtmp.new (1st pass) ....
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync: write failed on "/dbtmp.new/file.dmp": File too large (27)
rsync error: error in file IO (code 11) at receiver.c(258) [receiver=2.6.9]
rsync: connection
2014 Oct 27
3
"No free sectors available" while try to extend logical volumen in a virtual machine running CentOS 6.5
I'm trying to extend a logical volume and I'm doing as follow:
1- Run `fdisk -l` command and this is the output:
Disk /dev/sda: 85.9 GB, 85899345920 bytes 255 heads, 63 sectors/track,
10443 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes I/O size
(minimum/optimal): 512 bytes / 512 bytes Disk identifier: