How to stop kernel ext4 journaling thread so I can run fsck?
- From: Wayne <nospam@xxxxxxxxxxx>
- Date: Fri, 01 Jun 2012 19:25:45 -0400
Recently I wanted to manually run fsck on /home, so
I unmounted it (successfully). But fsck claimed the
device was busy! So it was, by a kernel thread. You
can't kill -9 those. Shouldn't such threads stop when the
associated device is unmounted? If not, how does one
stop it (or better, how should one run fsck on an ext4 FS)?
What I ended up doing was:
# touch /forcefsck; reboot
But is this a ext4 and/or kernel bug, or have I missed something?
Here's my system info, if it helps (Note I have remounted /home):
$ mount |grep sda5
/dev/sda5 on /home type ext4
(rw,nodev,relatime,seclabel,user_xattr,acl,barrier=1,data=ordered,usrquota)
$ ps -ef | grep sda5
root 626 2 0 01:01 ? 00:00:00 [jbd2/sda5-8]
$ rpm -q e2fsprogs
e2fsprogs-1.41.14-2.fc15.i686
$ uname -a
Linux XXXXXX 3.3.7-1.fc16.i686.PAE #1 SMP Tue May 22 14:07:22 UTC 2012 i686 i686 i386
GNU/Linux
$ lsb_release -a
LSB Version: :core-4.0-ia32:core-4.0-noarch
Distributor ID: Fedora
Description: Fedora release 16 (Verne)
Release: 16
Codename: Verne
--
Wayne
.
- Prev by Date: kernel trapped when reserving memory during booting with bootargs's mem
- Next by Date: Re: Monitors
- Previous by thread: kernel trapped when reserving memory during booting with bootargs's mem
- Next by thread: extracting URLs and IPs from zonefiles - easily :-)
- Index(es):
Relevant Pages
|
