From: luvar@plaintext.sk
To: linux-ext4@vger.kernel.org
Subject: corrupted fs, one nonreadable file after fsck
Date: Mon, 28 Mar 2016 16:05:17 +0100 (GMT+01:00) [thread overview]
Message-ID: <1878773164.36091459177517419.JavaMail.root@shiva> (raw)
In-Reply-To: <1562711781.36071459177448171.JavaMail.root@shiva>
Hi here, I have trouble with one lost file. fsck does not print any problem, but cat on file will print "No such device or address". diff prints something like "is a block special file while file".
Background:
I have raid10 (layout -n3) on mdraid. On top of that some lvm and in one volume I have ext4 fs. I have had some problems with out of sync mdraid, which I have fixed, so I do not know why fsck found a while ago some problems. They are all now "fixed" and fsck -fFn founds nothing.
fsck.ext4 -V
e2fsck 1.42.9 (4-Feb-2014)
Using EXT2FS Library version 1.42.9, 4-Feb-2014
Thanks for info,
LuVar
parent reply other threads:[~2016-03-28 15:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1562711781.36071459177448171.JavaMail.root@shiva>]
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=1878773164.36091459177517419.JavaMail.root@shiva \
--to=luvar@plaintext.sk \
--cc=linux-ext4@vger.kernel.org \
/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).