From: mross@rs-net.org
To: reiserfs-list@namesys.com
Subject: reiser4 corruption
Date: Fri, 17 Jun 2005 11:26:49 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0506171108440.6542@localhost> (raw)
I recently experimented using reiser4 on a backup system that processes
millions of files (most hard links to a main pool of files) every night. I
installed it on a spare machine by patching a vanilla 2.6.11.11 with the
reiser4 patches. Everything keep working for a few days, but I suddenly
noticed this message displayed multiple times:
reiser4[ktxnmgrd:md0:ru(1754)]: commit_current_atom
(fs/reiser4/txnmgr.c:1147)[nikita-3176]:
WARNING: Flushing like mad: 16384
as well as:
reiser4[pdflush(28040)]: commit_current_atom
(fs/reiser4/txnmgr.c:1147)[nikita-3176]:
WARNING: Flushing like mad: 16384
Would someone mind explaining to me what this means? Upon fscking, it
complained about one node containing an unrecognizable module, or
something similar. Unfortunately, I don't have the exact output. Also, the
semantic checks would have taken 2-3 full days to finish, so I didn't even
let fsck finish. I just moved back to reiserfs, which is a shame since
reiser4 was incredibly faster. (Simultaneous backups were going at a rate
of ~20MB/s compared to ~8MB/s on reiserfs)
Thanks,
-Ross
next reply other threads:[~2005-06-17 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 15:26 mross [this message]
2005-06-17 17:08 ` reiser4 corruption Edward Shishkin
2005-06-17 17:50 ` mross
2005-06-20 10:35 ` Vladimir Saveliev
-- 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-05-18 22:12 Reiser4 Corruption Craig Shelley
2004-09-04 18:07 reiser4 corruption Grzegorz Jaśkiewicz
2004-09-04 18:08 ` Grzegorz Jaśkiewicz
2004-09-04 18:23 ` Vince
2004-09-04 18:34 ` Grzegorz Jaśkiewicz
2004-05-22 19:36 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=Pine.LNX.4.60.0506171108440.6542@localhost \
--to=mross@rs-net.org \
--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).