reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 13536] crash while copying atime with touch
Date: Tue, 25 Aug 2009 21:01:33 GMT	[thread overview]
Message-ID: <200908252101.n7PL1XHs019270@demeter.kernel.org> (raw)
In-Reply-To: <bug-13536-695@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=13536





--- Comment #27 from Roland Kletzing <devzero@web.de>  2009-08-25 21:01:32 ---
weird...

but as this is bugzilla for vanilla kernel and not suse kernel (which contains
suse patches) i would have taken kernel-vanilla... package from kotd.

mind trying that, too ?

regarding comment #23 - i`m a little bit unsure. now, what is the offending
mount option? atime, data=journal or both ?

if you`re unsure,too, please test again and post results of

noatime,data=journal 
noatime,data=ordered
atime,data=journal
atime,data=ordered


furthermore, contrary to vanilla kernel suse kernel has barrier=flush as
default in place. so i would also compare barrier=flush vs. barrier=none 

+config REISERFS_DEFAULTS_TO_BARRIERS_ENABLED
+       bool "Default to 'barrier=flush' in reiserfs"
+       depends on REISERFS_FS
+        help
+         Modern disk drives support write caches that can speed up writeback.
+         Some devices, in order to improve their performance statistics,
+         report that the write has been completed even when it has only
+         been committed to volatile cache memory. This can result in
+         severe corruption in the event of power loss.
+
+         The -o barrier option enables the file system to direct the block
+         layer to issue a barrier, which ensures that the cache has been
+         flushed before proceeding. This can produce some slowdown in
+         certain environments, but allows higher end storage arrays with
+         battery-backed caches to report completes writes sooner than
+         would be otherwise possible.
+
+         Without this option, disk write caches should be disabled if
+         you value data integrity over writeback performance.
+
+         If unsure, say N.
+

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2009-08-25 21:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 11:33 [Bug 13536] New: crash while copying atime with touch bugzilla-daemon
2009-06-14 11:34 ` [Bug 13536] " bugzilla-daemon
2009-06-14 11:36 ` bugzilla-daemon
2009-06-14 11:37 ` bugzilla-daemon
2009-06-14 11:54 ` bugzilla-daemon
2009-06-14 22:45 ` bugzilla-daemon
2009-06-15 16:29 ` bugzilla-daemon
2009-06-15 16:33 ` bugzilla-daemon
2009-06-15 17:36 ` bugzilla-daemon
2009-06-18 13:53 ` bugzilla-daemon
2009-06-18 13:54 ` bugzilla-daemon
2009-06-18 13:56 ` bugzilla-daemon
2009-08-11 14:33 ` bugzilla-daemon
2009-08-12  9:10 ` bugzilla-daemon
2009-08-15 16:19 ` bugzilla-daemon
2009-08-15 18:50 ` bugzilla-daemon
2009-08-18  7:32 ` bugzilla-daemon
2009-08-18  7:56 ` bugzilla-daemon
2009-08-18  9:07 ` bugzilla-daemon
2009-08-18  9:21 ` bugzilla-daemon
2009-08-20 10:27 ` bugzilla-daemon
2009-08-22  8:53 ` bugzilla-daemon
2009-08-23 20:44 ` bugzilla-daemon
2009-08-23 20:48 ` bugzilla-daemon
2009-08-23 21:00 ` bugzilla-daemon
2009-08-23 21:00 ` bugzilla-daemon
2009-08-23 22:29 ` bugzilla-daemon
2009-08-25 20:07 ` bugzilla-daemon
2009-08-25 21:01 ` bugzilla-daemon [this message]
2009-08-28 12:19 ` bugzilla-daemon
2009-10-21 11:00 ` bugzilla-daemon
     [not found] <bug-13536-695@https.bugzilla.kernel.org/>
2012-06-08 11:57 ` bugzilla-daemon
2012-06-08 11:57 ` bugzilla-daemon

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=200908252101.n7PL1XHs019270@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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).