From: V10lator <v10lator@myway.de>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Unrecoverable FS errors
Date: Sun, 29 Jan 2017 19:14:10 +0100 [thread overview]
Message-ID: <f140bf03-3b2d-4e34-acec-423aa6323c19@myway.de> (raw)
In-Reply-To: <20170129041446.GC65555@jaegeuk.local>
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
>> 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.
>
> Which version of fsck.f2fs did you use?
> I suspect the version may be too old. You can get the latest one from:
>
> http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/log/?h=dev-test
>
> Thanks,
>
>> Today I noticed my package manager unlinking a death link but
>> that failed,
>> so I looked into the directory for myself:
>>
>> ls /etc/ssl/certs/ | grep EBG_Elektronik
>> EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
>>
>>
>> so the file is there, let's look closer: ...
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2017-01-29 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 12:11 Unrecoverable FS errors V10lator
2017-01-29 4:14 ` Jaegeuk Kim
2017-01-29 18:14 ` V10lator [this message]
2017-01-30 23:22 ` Jaegeuk Kim
2017-02-01 17:59 ` V10lator
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f140bf03-3b2d-4e34-acec-423aa6323c19@myway.de \
--to=v10lator@myway.de \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).