From: Jeff Mahoney <jeffm@suse.com>
To: tomnm <tomm@lime-technology.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: (reiserfs 3.6) sync command causes continuous writes
Date: Thu, 13 Jun 2013 18:34:37 -0400 [thread overview]
Message-ID: <51BA48FD.5060303@suse.com> (raw)
In-Reply-To: <loom.20130611T104322-574@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On 6/11/13 4:57 AM, tomnm wrote:
> After typing the 'sync' command all reiserfs 3.6 mounted volumes will be
> continuously written. For example, suppose 'sdb1' contains a reiserfs
> partition.
>
> mount /dev/sdb1 /mnt/data
>
> Now type:
> cat /sys/block/sdb/stat
> and note the number of I/O's to the partition.
> wait a couple seconds, look at I/O statistics and see they don't change.
>
> Now type:
> sync
>
> Subsequently typing 'cat /sys/block/sdb/stat' every few seconds shows
> increasing I/O.
>
> This can be confirmed by trying to spin the drive down:
> hdparm -y /dev/sdb
>
> The device spins down but then immediately spins back up due to above I/O
> taking place.
>
> If you umount the drive and mount again, the continuous I/O stops, only to
> resume again as soon as you type 'sync'.
>
> This behavior started with 3.5 kernel. All 3.4.x kernels are ok. All 3.5.x
> and newer kernels exhibit this behavior.
>
> This does not seem to occur with ext3 or FAT.
This looks like it is a side effect of commit 033369d1 (reiserfs: get
rid of resierfs_sync_super).
I haven't looked at it deeply enough to understand why it's getting
kicked off by the sync.
I think the right answer is to remove the new code added by that commit.
The superblock is always journaled when we modify it, so we don't need
to do the periodic flushing.
-Jeff
--
Jeff Mahoney
SUSE Labs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
prev parent reply other threads:[~2013-06-13 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 8:57 (reiserfs 3.6) sync command causes continuous writes tomnm
2013-06-11 9:16 ` dE
2013-06-13 22:34 ` Jeff Mahoney [this message]
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=51BA48FD.5060303@suse.com \
--to=jeffm@suse.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=tomm@lime-technology.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).