reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dushan Tcholich" <dusanc@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Fwd: [BUG] reiser4-for-2.6.22-2 Large stalls when using atime mount option
Date: Fri, 9 Nov 2007 15:04:28 +0100	[thread overview]
Message-ID: <a08621850711090604p305c3100m1f664b61d1799226@mail.gmail.com> (raw)
In-Reply-To: <a08621850711090603i304e38efuae936c73a056da63@mail.gmail.com>

---------- Forwarded message ----------
From: Dushan Tcholich <dusanc@gmail.com>
Date: Nov 9, 2007 3:03 PM
Subject: Re: [BUG] reiser4-for-2.6.22-2 Large stalls when using atime
mount option
To: Edward Shishkin <edward.shishkin@gmail.com>


There were some stalls, but a lot shorter than before (~7sec on
shutdown with patch, ~3.5min without), and no kernel messages.
Stalls that were encountered during normal use were short 1-3sec.
Take all this with a grain of salt because, for me, these are hard to reproduce.
kernel2.6.22-r8+reiser-for-2.6.22-2.patch+reiser4-discard-entd.patch
reiser4 mounted as / without -noatime option.

Dusan




On Nov 9, 2007 2:04 AM, Edward Shishkin <edward.shishkin@gmail.com> wrote:
> Hello guys.
> This is the promised patch against (2.6.22 + reiser4-for-2.6.22-2).
>
> Note, that this patch may cause problems, so keep also a stable kernel
> to boot on.
> The goal is to detect any progress in preventing the nasty stalls:
> please boot to the
> patched kernel and try to reproduce them. If you encounter oops, then
> reboot to the
> same kernel and try again. If oopses are annoying, then boot to the
> stable kernel and
> let me know about it.
>
> Waiting for your results..
> Thanks,
> Edward.
>
>
> On 11/8/07, Dushan Tcholich <dusanc@gmail.com> wrote:
> > Hi
> >
> > On Nov 7, 2007 10:31 PM, Edward Shishkin <edward.shishkin@gmail.com> wrote:
> > > Hello.
> > >
> > > On 11/7/07, Dushan Tcholich <dusanc@gmail.com> wrote:
> > > > Kernel: Gentoo 2.6.22-r2 + reiser4-for-2.6.22-2.patch
> > > > fstab:
> > > > /dev/sda2        /boot        ext2        noauto,noatime    1 2
> > > > /dev/sda5        /        reiser4                0 0
> > > > /dev/sda3        none        swap        sw        0 0
> > > > /dev/sda6        /home        ext3        noatime        0 0
> > > >
> > > > reiser4 partition is with cryptocompress (lzo) default settings.
> > > >
> > > > I usually mount r4 with -noatime, but after some debbuging with some users
> > > > on irc (rvalles), who have intermitent large stalls, we found that only
> > > > difference between our setups was my -noatime flag in fstab.
> > >
> > > Plus rvalles doesn't use compression (isn't it?)
> >
> > He had stalls without compression, but now switched to compression and
> > still has them.
> > But I can't reproduce them with -noatime option.
> > >
> > > > I tried to mount / without -noatime, started gnome, and then in about same
> > > > time evolution, firefox, played some mp3s, avis, did a kernel compile,
> > > > emerge -uD world (compiled few packages), acessed some random fles in
> > > > /usr/src/linux, started gnome disk usage analyser etc. and had no stalls at
> > > > all.
> > > > And then I tried to reboot. System stalled for 3min 25 sec (i was ready with
> > > > a watch :)) before printing the first message, with heavy disk activity.
> > > > Upon reboot I just changed line in fstab with nano to mount r4 with -noatime
> > > > and rebooted agin. Now there were no stalls.
> > > >
> >
> > To my inexperienced eyes it looks like lazy writes of atime are adding
> > with that "reiser4 writes continuously to same sector" bug.
> >
> > >
> > > Currently I am preparing a patch for this problem.
> > > Not sure about its efficiency: we'll take a look..
> >
> > Great
> >
> > >
> > > Thanks,
> > > Edward.
> > >
> >
> > Dushan
> >
>

  parent reply	other threads:[~2007-11-09 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a08621850711071223w30e5f74bua8e8189efb6814a7@mail.gmail.com>
2007-11-07 21:31 ` [BUG] reiser4-for-2.6.22-2 Large stalls when using atime mount option Edward Shishkin
2007-11-08  8:52   ` Dushan Tcholich
     [not found]     ` <5c7c368b0711081704w2ff39c59r4ad10a37a6de924a@mail.gmail.com>
     [not found]       ` <a08621850711090603i304e38efuae936c73a056da63@mail.gmail.com>
2007-11-09 14:04         ` Dushan Tcholich [this message]
     [not found] ` <a08621850711111326i5248f9efhf04d7ea664d12ae9@mail.gmail.com>
     [not found]   ` <5c7c368b0711111338p7689512cia010c608d071dd34@mail.gmail.com>
     [not found]     ` <a08621850711111359x79c2b5dep7f078edd647bfe99@mail.gmail.com>
     [not found]       ` <5c7c368b0711140615i4c7566c2o36c81a9b8861ea34@mail.gmail.com>
     [not found]         ` <a08621850711141135w7709d3b6i63fa1454b12f2606@mail.gmail.com>
     [not found]           ` <a08621850711141153o105aa784t2c270b74a36a1899@mail.gmail.com>
     [not found]             ` <a08621850711141159k34a8ea1bk709c93cc1076d071@mail.gmail.com>
     [not found]               ` <a08621850711141201l4e322c57x6a9c5021ec147f0a@mail.gmail.com>
     [not found]                 ` <a08621850711141224x1d361c86w287e1c6dcadc1ff1@mail.gmail.com>
2007-11-14 21:17                   ` 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=a08621850711090604p305c3100m1f664b61d1799226@mail.gmail.com \
    --to=dusanc@gmail.com \
    --cc=reiserfs-devel@vger.kernel.org \
    /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).