Am Dienstag, 31. Januar 2017 00:22:52 CET schrieb Jaegeuk Kim:
> On 01/29, V10lator wrote:
>> Hi,
>>
>> I compiled and tried the version you linked, sadly it's still the same.
>
> Oh, was there no reported error?
Yes there was, sorry for not showing earlier:
Info: Force to fix corruption
Info:
On 01/29, V10lator wrote:
> Hi,
>
> I compiled and tried the version you linked, sadly it's still the same.
Oh, was there no reported error?
Then, which kernel version are you using?
Thanks,
>
> Thanks for your support
>
> Am Sonntag, 29. Januar 2017 05:14:46 CET schrieb Jaegeuk Kim:
> > Hi,
Hi,
I compiled and tried the version you linked, sadly it's still the same.
Thanks for your support
Am Sonntag, 29. Januar 2017 05:14:46 CET schrieb Jaegeuk Kim:
> Hi,
>
> On 01/27, V10lator wrote:
>> Hi,
>>
>> First off if this is the wrong mailing list please tell me, I
>> just couldn't
>>
Hi,
On 01/27, V10lator wrote:
> Hi,
>
> First off if this is the wrong mailing list please tell me, I just couldn't
> find any other for f2fs.
>
> Around a year (maybe longer) ago my computer crashed, the only way was a
> hard reset which caused f2fs corruptions. Since then fsck.f2fs -f finds
Hi,
First off if this is the wrong mailing list please tell me, I just couldn't
find any other for f2fs.
Around a year (maybe longer) ago my computer crashed, the only way was a
hard reset which caused f2fs corruptions. Since then fsck.f2fs -f finds
errors. These are always the same errors.
