If there are no further questions, I will format the stick this weekend.
On Tue, Nov 19, 2013 at 4:34 PM, tast ky wrote:
> Hello again,
>
> after buying a new USB stick and moving everything but the partition's
> broken file & folder to it, I am now able to send you an image after
> all.
>
> Alth
Hello again,
after buying a new USB stick and moving everything but the partition's
broken file & folder to it, I am now able to send you an image after
all.
Although the 21 GB partition was supposed to only contain those two
tiny entries, df still reported 1.8 GB as in use.
I did "dd if=/dev/ze
Hi,
2013-10-22 (화), 22:50 +0200, Max Muster:
> Hi,
>
> I don't recall anything like a blackout, but since I like to run new
> software that's still in development, I have had a fair share of system
> crashes.
>
> As far as I'm aware this is the only file on the partition to ever
> become corrupt
Hi,
I don't recall anything like a blackout, but since I like to run new
software that's still in development, I have had a fair share of system
crashes.
As far as I'm aware this is the only file on the partition to ever
become corrupted at the file system level, though.
The repository was a sim
Hi,
Thank you for the report.
2013-10-19 (토), 19:36 +0200, Max Muster:
> There's a broken, ie. inaccessible and unerasable file on my f2fs
> partition (2nd partition with 21GB on a Corsair Flash Voyager GT USB 3.0
> 32GB). ls reports:
>
> >cannot access shared.h: Input/output error
> >total 0
There's a broken, ie. inaccessible and unerasable file on my f2fs
partition (2nd partition with 21GB on a Corsair Flash Voyager GT USB 3.0
32GB). ls reports:
>cannot access shared.h: Input/output error
>total 0
>-? ? ? ? ?? shared.h
The file has been on the partition for a
