Displaying 6 results from an estimated 6 matches for "137k".
Did you mean:
137
2006 Jul 03
8
[raidz] file not removed: No space left on device
On a system still running nv_30, I''ve a small RaidZ filled to the brim:
2 3 root at mir pts/9 ~ 78# uname -a
SunOS mir 5.11 snv_30 sun4u sparc SUNW,UltraAX-MP
0 3 root at mir pts/9 ~ 50# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mirpool1 33.6G 0 137K /mirpool1
mirpool1/home 12.3G 0 12.3G /export/home
mirpool1/install 12.9G 0 12.9G /export/install
mirpool1/local 1.86G 0 1.86G /usr/local
mirpool1/opt 4.76G 0 4.76G /opt
mirpool1/sfw 752M 0 752M /usr/sfw
Trying to free som...
2012 Dec 21
4
zfs receive options (was S11 vs illumos zfs compatiblity)
> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss-
> bounces at opensolaris.org] On Behalf Of bob netherton
>
> You can, with recv, override any property in the sending stream that can
> be
> set from the command line (ie, a writable).
>
> # zfs send repo/support at cpu-0412 | zfs recv -o version=4 repo/test
> cannot receive: cannot override received
2009 Apr 10
3
Local disk rsync
I've done quite a bit of looking, but I haven't found an answer that
answers this question.
Environment:
cygwin on Windows
rsync 3.0.4
I know that rsync isn't optimzed for speed on local copies - that's
clear in my testing. I'm attemting to sync a large volume of files.
(In this case, I'm syncing a rdiff-backup set...)
An initial sync will be about one fourth as fast a
2014 Mar 07
2
Syslinux EFI + TFTPBOOT Support
On 2014?03?07? 23:05, Ady wrote:
> I understand that these remarks might seem not the main issue, but I
> tend to think that once you are successful while using only "default"
>
> values and in a minimalistic case, you could add complexity
> (different paths, multiple firmwares, additional kernels, multiple
> cfg files...).
Ady,
Thanks. I will follow your advice to
2014 Mar 08
2
Syslinux EFI + TFTPBOOT Support
...rt 1758
--mcast-addr 239.255.0.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5
--port 69 /tftpboot/nbi_img/"
====================
Files are in the correct path:
ls -alFh /tftpboot/nbi_img/{*.efi,*e64}
-rw-r--r-- 1 root root 179K Mar 7 21:41 /tftpboot/nbi_img/bootx64.efi
-rw-r--r-- 1 root root 137K Mar 7 21:41 /tftpboot/nbi_img/ldlinux.e64
and they were extracted from prebuilt binary 6.03-pre7 tarball on
kernel.org:
sha1sum /tftpboot/nbi_img/{*.efi,*e64}
d0ca7d52228231b08c36967262cb796be9e71499 /tftpboot/nbi_img/bootx64.efi
55f17d57e1790071af0cb84e0ac6109a210f06ca /tftpboot/nbi_img/ldlinu...
2010 Mar 04
8
Huge difference in reporting disk usage via du and zfs list. Fragmentation?
Do we have enormous fragmentation here on our X4500 with Solaris 10, ZFS Version 10?
What except zfs send/receive can be done to free the fragmented space?
One ZFS was used for some month to store some large disk images (each 50GByte large) which are copied there with rsync. This ZFS then reports 6.39TByte usage with zfs list and only 2TByte usage with du.
The other ZFS was used for similar