linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shridhar Daithankar <ghodechhap@ghodechhap.net>
To: linux-btrfs@vger.kernel.org
Subject: unclean shutdown and space cache rebuild
Date: Sun, 30 Jun 2013 19:26:16 +0530	[thread overview]
Message-ID: <11441914.sRzrmH57Vq@bheem> (raw)

Hello,

I have 3 partitions with btrfs(/, /home and /data). All of them have following 
mount options

noatime,space_cache,inode_cache,compress=lzo,defaults

Whenever there is a unclean shutdown(which happens a lot in my case), the next 
reboot, system comes up relatively at the same speed but as systemd is 
starting up daemons, the disk is continuously ( and unusally long) grinding.

This causes random delays with various daemons such as postgresql failing to 
start, kdm timing out of xorg servers etc and I have to reboot after the dust 
settles to bring back the system to the normal. At one time, even 
keyboad/mouse were not responding as some debus service timed out..

I think it is rebuilding the space cache because I saw similar long disk 
activity when I activated it first.

How can I confirm that it is the space cache rebuild thats taking time?

if space cache rebuild is the reason, is there any way to improve it? 

I am running archlinux/systemd/kde setup with two 7200 RPM seagate sata 
disks(no RAID, one 80 GB for / and /home, other 500GB for data). The kernel is 
3.9.8 x86_64.

Thanks.

-- 
Regards
 Shridhar

             reply	other threads:[~2013-06-30 13:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 13:56 Shridhar Daithankar [this message]
2013-06-30 17:53 ` unclean shutdown and space cache rebuild Garry T. Williams
2013-06-30 19:58   ` Pete
2013-06-30 20:10   ` Clemens Eisserer
2013-06-30 21:20   ` Duncan
2013-06-30 23:12   ` Roger Binns
2013-07-01  2:50   ` Shridhar Daithankar
2013-07-01  9:10     ` Duncan
2013-07-01 16:19       ` Shridhar Daithankar
2013-07-02 13:00         ` Duncan
2013-07-02 15:49           ` Shridhar Daithankar
2013-07-05  3:45             ` Shridhar Daithankar

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=11441914.sRzrmH57Vq@bheem \
    --to=ghodechhap@ghodechhap.net \
    --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).