From: "Jonáš Vidra" <vidra.jonas@seznam.cz>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: ReiserFS mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: Segfault in fsck.reiser4
Date: Tue, 23 Mar 2010 22:43:52 +0100 [thread overview]
Message-ID: <op.u91inegqhogzsi@g17b> (raw)
In-Reply-To: <4BA9240D.4080705@gmail.com>
Dne Tue, 23 Mar 2010 21:26:53 +0100 Edward Shishkin
<edward.shishkin@gmail.com> napsal(a):
> The most efficient way is to provide me with a root access to your
> machine.
> You have encountered a rare case of corruption, and it is important to
> fix this fsck bug properly.
Well …
I don't think that would be possible, but I'll see what I can do.
Several users have accounts on the machine, so even though they are just
family members, not corporate customers, I can't allow everyone in.
I'd like to help, so I'll try to arrange it somehow.
>> By the way, how do I find a filename by node number or key?
>
> find - inum 64881
Thanks. That's straightforward, shame on me for asking stupid questions.
>> I'd like to know which file caused the corruption.
>
> What do you want to do with this file?
I'd like to know if it is backed up somewhere, unique
or downloaded from the Internet or whatever.
I know I can't really trust *any* data on this partition anymore,
but I'd still like to know which files are the most likely to be lost.
--
Jonáš Vidra
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-23 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 17:30 Segfault in fsck.reiser4 Jonáš Vidra
2010-03-23 20:26 ` Edward Shishkin
2010-03-23 20:31 ` Edward Shishkin
2010-03-23 21:43 ` Jonáš Vidra [this message]
2010-03-23 22:31 ` Edward Shishkin
2010-03-24 8:54 ` Vidra.Jonas
2010-03-24 13:10 ` Edward Shishkin
2010-03-27 8:38 ` Jonáš Vidra
2010-03-30 0:59 ` Edward Shishkin
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=op.u91inegqhogzsi@g17b \
--to=vidra.jonas@seznam.cz \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.