From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 26642] New: Automatically clean dirty bit on ext2/ext4-without-journal file systems
Date: Thu, 13 Jan 2011 15:18:25 GMT [thread overview]
Message-ID: <bug-26642-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=26642
Summary: Automatically clean dirty bit on
ext2/ext4-without-journal file systems
Product: File System
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: enhancement
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: t.artem@mailcity.com
Regression: No
In ext2/journalless ext4 if you forget to umount the FS before
rebooting/powering down PC you'll have to run fsck on a next boot. That's
obvious.
However we can easily avoid fsck'ing if we clean the dirty bit about a certain
timeout (I suggest a configurable 300 seconds value) and only after dirty
buffers have been flushed to the disk. If we write to the disk again, then this
bit should be set again, of course.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-01-13 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 15:18 bugzilla-daemon [this message]
2011-01-13 18:42 ` [Bug 26642] Automatically clean dirty bit on ext2/ext4-without-journal file systems bugzilla-daemon
2011-01-13 23:47 ` bugzilla-daemon
2011-01-14 3:23 ` bugzilla-daemon
2012-08-14 15:36 ` bugzilla-daemon
2012-08-14 15:41 ` bugzilla-daemon
2012-08-14 18:33 ` 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=bug-26642-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).