Error 28

GNU Radio
#1

I have a USRP source going direct to a file sink, and it runs really
well,
except for an error. Does anyone know what the following means?:

thread[thread-per-block[1]: <block file_sink (2)>]: file_sink write
failed
with error 28

I am writing to a RAMDisk, if that helps with a solution.

Thank you.

#2

On Thu, Dec 5, 2013 at 12:04 PM, Paul B. Huter
[email protected]n.invalidwrote:

I have a USRP source going direct to a file sink, and it runs really well,
except for an error. Does anyone know what the following means?:

thread[thread-per-block[1]: <block file_sink (2)>]: file_sink write failed
with error 28

it means that you’re out of space (
http://www.virtsync.com/c-error-codes-include-errno) on the device

–

This email, including any attachments, is only for the intended
recipient.
It is subject to copyright, is confidential and may be the subject of
legal
or other privilege, none of which is waived or lost by reason of this
transmission.
If you are not an intended recipient, you may not use, disseminate,
distribute or reproduce such email, any attachments, or any part
thereof.
If you have received a message in error, please notify the sender
immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or
corrupted during transmission nor can we guarantee that any email or any
attachments are free from computer viruses or other conditions which may
damage or interfere with recipient data, hardware or software. The
recipient relies upon its own procedures and assumes all risk of use and
of
opening any attachments.

#3

Useful list! Thank you!

On Wed, Dec 4, 2013 at 5:35 PM, Mark Cottrell

#4

Useful list! Thank you!
That code comes from “errno”, which are the integer return codes from
system calls.

Many Linuxes have a “perror” command line tool that can translate these
into text:

perror 28

Might have worked for you. Although, it’s considered “polite” for
programs, when getting an error return from a kernel call to
use the programmatic equivalent of “perror” on return codes to give a
more meaningful result.

–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org