Displaying 3 results from an estimated 3 matches for "165g".
Did you mean:
165
2010 Feb 08
5
zfs send/receive : panic and reboot
<copied from opensolaris-dicuss as this probably belongs here.>
I kept on trying to migrate my pool with children (see previous threads) and had the (bad) idea to try the -d option on the receive part.
The system reboots immediately.
Here is the log in /var/adm/messages
Feb 8 16:07:09 amber unix: [ID 836849 kern.notice]
Feb 8 16:07:09 amber ^Mpanic[cpu1]/thread=ffffff014ba86e40:
Feb 8
2003 Sep 04
1
rsync 2.5.6, No buffer space available error...
I have seen this error in many postings, but the solutions seem not to
apply in this case. This error happens during a small file transfer
(gif image) and after 75% of a 165G rsync job (the building file list
portion is complete.) Most solutions I saw were related to not having
enough RAM or running out of disk space. Check out the machine specs
below the error.
rsync: writefd_unbuffered failed to write 4830 bytes: phase "unknown":
No buffer space avail...
2004 Jan 30
1
rsync 2.5.6, No buffer space available error...
> On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote:
>> I have seen this error in many postings, but the solutions seem not to
>> apply in this case. This error happens during a small file transfer
>> (gif image) and after 75% of a 165G rsync job (the building file list
>> portion is complete.) Most solutions I saw were related to not having
>> enough RAM or running out of disk space. Check out the machine specs
>> below the error.
>>
>> rsync: writefd_unbuffered failed to write 4830 bytes: phas...