From: <doiggl@velocitynet.com.au>
To: "Jonáš Vidra" <vidra.jonas@seznam.cz>
Cc: ReiserFS mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: how can I list out any replayed journal entries on startup in reiser4 filesystem
Date: Sun, 13 Feb 2011 01:06:21 +1100 [thread overview]
Message-ID: <3f7c92853e755d5e74db17f2885f41dd@mail.velocitynet.com.au> (raw)
In-Reply-To: <op.vqr6rm2phogzsi@g17b>
On Sat, 12 Feb 2011 09:20:06 +0100, Jonáš Vidra <vidra.jonas@seznam.cz>
wrote:
> Dne Sat, 12 Feb 2011 04:20:13 +0100 <doiggl@velocitynet.com.au>
napsal(a):
>
>> Hello,
>> I ask because the activation time on /dev/sdb -> /media/disk is 130
>> seconds or so with no progress on screen , so for me its helpful to see
a
>> progress indicator and a pass/fail at the end of journal replay
process.
>> Glenn
>
> Umount your partitions properly and use fsck if you don't. But I don't
> think this is caused by a journal replay. How big is that disk? You may
> consider using the "dont_load_bitmap" option — just put it into your
> fstab or use the "-o" switch when you mount the FS.
> How big is that disk?
1.7Terabyte | 1.1T used | 600 GB free |371,987 files, all on one
partition
Is this the correct format for dont_load_bitmap in /etc/fstab ?
/dev/sdb /media/disk reiser4 defaults,dont_load_bitmap 0 0
--
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:[~2011-02-12 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 0:33 how can I list out any replayed journal entries on startup in reiser4 filesystem doiggl
2011-02-12 1:30 ` Edward Shishkin
2011-02-12 3:20 ` doiggl
2011-02-12 8:20 ` Jonáš Vidra
2011-02-12 14:06 ` doiggl [this message]
2011-02-12 14:21 ` 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=3f7c92853e755d5e74db17f2885f41dd@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@vger.kernel.org \
--cc=vidra.jonas@seznam.cz \
/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).