linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: superblock checksum mismatch after crash, cannot mount
Date: Sun, 24 Aug 2014 22:49:51 +1000	[thread overview]
Message-ID: <2850101.SbkCu8D9cB@quad> (raw)
In-Reply-To: <20140824110853.GB22693@apia.perrit.net>

On Sun, 24 Aug 2014 01:08:53 PM Leen Besselink wrote:

> tip for basically any Linux filesystem, especially on Flash-based storage
> and also btrfs: - use noatime (if you aren't doing that already, don't know
> if that is the default in btrfs)

Since 2.6.30 (5 years old now) the kernel has defaulted to mounting filesystems
with relatime not atime so it's not as bad as it used to be.  This is from the mount
manual page.

       relatime
              Update inode access times relative to modify or change time.  Access time is  only
              updated  if the previous access time was earlier than the current modify or change
              time. (Similar to noatime, but doesn't break mutt or other applications that  need
              to know if a file has been read since the last time it was modified.)

              Since  Linux  2.6.30,  the kernel defaults to the behavior provided by this option
              (unless noatime was  specified), and the strictatime option is required to  obtain
              traditional  semantics.  In  addition,  since Linux 2.6.30, the file's last access
              time is always  updated  if  it  is more than 1 day old.

All the best,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC



  reply	other threads:[~2014-08-24 12:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 22:00 superblock checksum mismatch after crash, cannot mount Florian Gamböck
2014-08-22 22:17 ` Florian Gamböck
2014-08-23  5:27 ` Duncan
2014-08-23  8:38   ` Florian Gamböck
2014-08-23  9:34     ` Duncan
2014-08-23 14:14       ` Florian Gamböck
2014-08-24 20:29         ` Chris Murphy
2014-08-23 16:38       ` Zygo Blaxell
2014-08-24  0:56         ` Duncan
2014-08-24  2:57           ` Chris Murphy
2014-08-24 11:08           ` Leen Besselink
2014-08-24 12:49             ` Chris Samuel [this message]
2014-08-24 12:59             ` Duncan
2014-08-24 14:09             ` Florian Gamböck
  -- strict thread matches above, loose matches on Subject: below --
2014-08-24 16:59 Flash ROM
2014-08-24 18:41 ` Florian Gamböck
2014-08-24 19:48 ` Chris Murphy
2014-08-25 11:42   ` Austin S Hemmelgarn

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=2850101.SbkCu8D9cB@quad \
    --to=chris@csamuel.org \
    --cc=linux-btrfs@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).