From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: read error on superblock
Date: Mon, 23 Jul 2012 10:45:10 +0200 [thread overview]
Message-ID: <19753282.RhzHOQAfKG@coil> (raw)
Hi list,
a harddrive got some bad sectors and now one NILFS filesystem can't be mounted;
mount: /dev/sda3: can't read superblock
I can (try to) copy this filesystem to another drive; how do I proceed form
that point? Does it make any sense to substitute another superblock for this
one? (either to use a spare superblock, if such exists, or put a new
superblock on the damaged sector(s)).
Regards,
--
dexen deVries
[[[↓][→]]]
"all dichotomies are either true or false" is a true paradox because it's
paradoxical only if it is a paradox ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-07-23 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 8:45 dexen deVries [this message]
2012-07-23 9:17 ` read error on superblock Vyacheslav Dubeyko
2012-07-23 9:24 ` dexen deVries
2012-07-23 9:37 ` Vyacheslav Dubeyko
2012-07-23 9:39 ` Ryusuke Konishi
[not found] ` <20120723.183907.154986664.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-23 9:42 ` dexen deVries
2012-07-23 11:06 ` dexen deVries
2012-07-23 11:19 ` Ryusuke Konishi
[not found] ` <20120723.201918.94868195.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-23 18:24 ` dexen deVries
2012-07-24 0:06 ` Ryusuke Konishi
[not found] ` <20120724.090604.40913934.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-24 6:26 ` Vyacheslav Dubeyko
2012-07-24 7:52 ` dexen deVries
2012-07-24 16:46 ` Ryusuke Konishi
[not found] ` <20120725.014653.38326039.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-24 20:05 ` Nick Martin
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=19753282.RhzHOQAfKG@coil \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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