reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Grzegorz Jaśkiewicz" <gryzman@gmail.com>
To: reiserfs-list@namesys.com
Subject: reiser4 corruption
Date: Sat, 4 Sep 2004 20:07:36 +0200	[thread overview]
Message-ID: <2f4958ff04090411072d5c767d@mail.gmail.com> (raw)

Hi folks

I have some issues with KDE compilation on my computer.
I decided to give it a try (and test), and switched over /home
partition on one of my laptops to reiserfs v4. I am using debian
testing (knoppix installation) + 2.6.9-mm1.

Recently I had some issues compiling KDE (acctually in linking) that
might have source in fs corruption. SO I decided to run fsck.reiser4.
Logged output is attached. Tell me please if it's any help, or if
something else should be done.
I don't have anything in logs, FS wasn't compiled with debug options.

I'll run --build-fs on it now. When it's finished, I'll remove KDE
sources, suck them again from CVS, and try to rebuild. And fsck again.
We'll see if it's reproducable.

thanks.

-- 
GJ

             reply	other threads:[~2004-09-04 18:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04 18:07 Grzegorz Jaśkiewicz [this message]
2004-09-04 18:08 ` reiser4 corruption Grzegorz Jaśkiewicz
2004-09-04 18:23 ` Vince
2004-09-04 18:34   ` Grzegorz Jaśkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2014-10-31 16:37 Reiser4 corruption dE
2014-10-31 17:26 ` Edward Shishkin
2014-11-01 11:16   ` dE
2014-11-01 12:47     ` Edward Shishkin
2014-11-01 16:05       ` dE
2005-06-17 15:26 reiser4 corruption mross
2005-06-17 17:08 ` Edward Shishkin
2005-06-17 17:50   ` mross
2005-06-20 10:35     ` Vladimir Saveliev
2005-05-18 22:12 Reiser4 Corruption Craig Shelley
2004-05-22 19:36 reiser4 corruption dave

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=2f4958ff04090411072d5c767d@mail.gmail.com \
    --to=gryzman@gmail.com \
    --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 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).