From: Dirk <noisyb@gmx.net>
To: "Łukasz Mierzwa" <prymitive@pcserwis.net>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: serious Reiser4 fsck problem
Date: Sat, 22 Jul 2006 12:33:56 +0200 [thread overview]
Message-ID: <44C1FF14.7040504@gmx.net> (raw)
In-Reply-To: <op.tc248azkd4os1z@localhost>
£ukasz Mierzwa wrote:
> Dnia Sat, 22 Jul 2006 12:08:58 +0200, Dirk <noisyb@gmx.net> napisa³:
>
>> Hello,
>> will using
>>
>> fsck.reiser4 --build-fs
>>
>> result in data loss? I mean to fix the partition - NOT to lose the data
>> on it..
>>
>> The manual page is also not very specific about if data will be lost or
>> not when using this option...
>>
>> Using --fix resulted in a message that I should use --build-fs to remove
>> corruption...
>
>
> You will probably end up with some amount of files in lost&found dir,
> those will be the files that fsck can't recognize from what dir are
> coming and what are named, depending on what corruption You have there
> can always be some files that You won't get back. As always, backups
> are a must have on any fs.
>
>
The hdd was full and a process was still trying to write and create new
files... So I guess those files might end up in lost+found...
Just want to make sure that --build-fs will not build a _new_ fs,
meaning formatting the fs by formatting it?!? That wasn't very clear
from what I'd read in the manual...
Dirk
next prev parent reply other threads:[~2006-07-22 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 10:08 serious Reiser4 fsck problem Dirk
2006-07-22 10:10 ` Łukasz Mierzwa
2006-07-22 10:33 ` Dirk [this message]
2006-07-24 14:47 ` Vladimir V. Saveliev
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=44C1FF14.7040504@gmx.net \
--to=noisyb@gmx.net \
--cc=prymitive@pcserwis.net \
--cc=reiserfs-list@namesys.com \
/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.