linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: V10lator <v10lator@myway.de>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Unrecoverable FS errors
Date: Sun, 29 Jan 2017 13:14:46 +0900	[thread overview]
Message-ID: <20170129041446.GC65555@jaegeuk.local> (raw)
In-Reply-To: <29539c24-f249-41c6-aa1e-d7851140e20c@myway.de>

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:
> 
> $ LANG=C ls -l /etc/ssl/certs/ | grep EBG_Elektronik
> ls: Zugriff auf 
> '/etc/ssl/certs/EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem' nicht 
> möglich: Datei oder Verzeichnis nicht gefunden
> l????????? ? ?    ?         ?             ? 
> EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
> 
> 
> Doesn't look good. One more try:
> 
> $ LANG=C file 
> /etc/ssl/certs/EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
> /etc/ssl/certs/EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem: cannot open 
> `/etc/ssl/certs/EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem' (No such 
> file or directory)
> 
> 
> Okay, so the file is clearly corrupted. Let's remove it:
> 
> # LANG=C LC_ALL=C rm 
> /etc/ssl/certs/EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
> rm: cannot remove 
> '/etc/ssl/certs/EBG_Elektronik_Sertifika_Hizmet_Sa'$'\304\237''lay'$'\304\261''c'$'\304\261''s'$'\304\261''.pem': 
> No such file or directory
> 
> 
> 
> Is there anything I can do to remove that file (or the directory entry as I 
> think there is no file) ?
> 
> Thanks,
> Thomas "V10lator" Rohloff
> 
> ------------------------------------------------------------------------------
> 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

------------------------------------------------------------------------------
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

  reply	other threads:[~2017-01-29  4:15 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 [this message]
2017-01-29 18:14   ` V10lator
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=20170129041446.GC65555@jaegeuk.local \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=v10lator@myway.de \
    /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).