What follows is an embarrassing tale.
Earlier today, I was un-tar'ing a source archive for a game I wanted to port. It was something like 200 MB or so. So I started the command and let it cook for a while, with a command to emit an audible beep when it was done. After a few minutes, I hear a beep and open up my pandora to check the terminal. I'm greeted with a bunch of messages to the effect of "Cannot write thus-and-such file: Read only file system.
It turns out I was un-tar'ing into my home directory on the NAND rather than the SD card.
Whoops.
So, I figure, I'll just rm -r the directory I had accidentally created and be on my merry way. Not so simple. Now I'm greeted by "Cannot remove thus-and-such: Read only file system." I try doing a chmod a+w on everything down to the root to no effect, I check my mount table and find that ubifs0 on "/" is mounted readonly so I remount it read-write, "mount" says it worked but I still can't remove the files (or write to NAND at all), and at the tail end of my dmesg I'm getting a bunch of errors to the effect of (I'm paraphrasing) "UBI_fs: make_reservation: cannot allocate thus-and-such number of bytes in thus-and-such jhead, error -30".
Rebooting doesn't help either.
I've heard that UBI-fs can't handle filling up or something. My current thought at this point is to reflash my NAND, is this really my only option? Does UBIfs really suck this much, or is there another explanation?
Earlier today, I was un-tar'ing a source archive for a game I wanted to port. It was something like 200 MB or so. So I started the command and let it cook for a while, with a command to emit an audible beep when it was done. After a few minutes, I hear a beep and open up my pandora to check the terminal. I'm greeted with a bunch of messages to the effect of "Cannot write thus-and-such file: Read only file system.
It turns out I was un-tar'ing into my home directory on the NAND rather than the SD card.
Whoops.
So, I figure, I'll just rm -r the directory I had accidentally created and be on my merry way. Not so simple. Now I'm greeted by "Cannot remove thus-and-such: Read only file system." I try doing a chmod a+w on everything down to the root to no effect, I check my mount table and find that ubifs0 on "/" is mounted readonly so I remount it read-write, "mount" says it worked but I still can't remove the files (or write to NAND at all), and at the tail end of my dmesg I'm getting a bunch of errors to the effect of (I'm paraphrasing) "UBI_fs: make_reservation: cannot allocate thus-and-such number of bytes in thus-and-such jhead, error -30".
Rebooting doesn't help either.
I've heard that UBI-fs can't handle filling up or something. My current thought at this point is to reflash my NAND, is this really my only option? Does UBIfs really suck this much, or is there another explanation?
