Something about "filesystems is NOT Clean"

igor1982 · 2011-08-26 12:34:54

I bought Thinkpad X1 recently. I install arch on it. Everything seems fine, except that "filesystems is NOT Clean" appears everytime when I start the laptop. I cannot find useful information from google. I just guess that it is a problem associated with unnormal shutdown procedure.

Any suggestions are welcome!

I use lvm2 to manage logical volumns.

$ sudo lvs
  LV   VG        Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  home archgroup -wc-ao 255.12g                                      
  root archgroup -wc-ao  19.53g                                      
  swap archgroup -wc-ao   3.91g                                      
  var  archgroup -wc-ao  19.53g

Here, "home" and "root" use the filesystem of "ext4" and "var" use "reisefs"。

The following is several informations from kernel.log which may be useful:

Aug 26 14:03:27 Igor-Home kernel: [  100.249270] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 26 14:03:38 Igor-Home kernel: [  111.193303] wlan0: no IPv6 routers present
Aug 26 14:04:26 Igor-Home kernel: [  158.867839] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 1
Aug 26 14:04:30 Igor-Home kernel: [  162.530151] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 84:c9:b2:49:55:9d tid = 0
Aug 26 14:04:48 Igor-Home kernel: [  180.416263] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 84:c9:b2:49:55:9d tid = 0
Aug 26 14:05:30 Igor-Home kernel: [  222.693282] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 7
Aug 26 14:05:39 Igor-Home kernel: [  231.802666] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 10
Aug 26 14:05:44 Igor-Home kernel: [  236.781757] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 84:c9:b2:49:55:9d tid = 0
Aug 26 14:06:10 Igor-Home kernel: [  262.689224] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 4
Aug 26 14:07:04 Igor-Home kernel: [  316.406812] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 1
Aug 26 14:07:56 Igor-Home kernel: [  367.799895] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:08:41 Igor-Home kernel: [  413.245620] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:10:59 Igor-Home kernel: [  550.827063] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:16:37 Igor-Home kernel: [  887.984073] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 84:c9:b2:49:55:9d tid = 0
Aug 26 14:19:30 Igor-Home kernel: [ 1060.306074] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:22:48 Igor-Home kernel: [ 1257.936197] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:25:18 Igor-Home kernel: [ 1407.916947] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:31:48 Igor-Home kernel: [ 1796.713849] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:34:45 Igor-Home kernel: [ 1973.279503] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:35:53 Igor-Home kernel: [ 2041.481879] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:38:02 Igor-Home kernel: [ 2169.723218] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 1
Aug 26 14:45:54 Igor-Home kernel: [ 2641.575445] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 14:51:18 Igor-Home kernel: [ 2964.068080] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 2
Aug 26 15:05:37 Igor-Home kernel: [ 3820.925654] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 1
Aug 26 15:12:50 Igor-Home kernel: [ 4253.483857] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 15:15:57 Igor-Home kernel: [ 4440.025743] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 15:18:28 Igor-Home kernel: [ 4591.024983] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 15:23:11 Igor-Home kernel: [ 4873.182426] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 2
Aug 26 15:29:05 Igor-Home kernel: [ 5225.756546] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 15:31:49 Igor-Home kernel: [ 5390.096634] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 1
Aug 26 15:36:06 Igor-Home kernel: [ 5646.766321] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 2
Aug 26 15:37:17 Igor-Home kernel: [ 5717.409054] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 15:41:28 Igor-Home kernel: [ 5967.637480] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 15:44:11 Igor-Home kernel: [ 6130.459235] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0
Aug 26 15:47:00 Igor-Home kernel: [ 6298.522120] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 0

Last edited by igor1982 (2011-08-26 14:38:19)

bernarcher · 2011-08-26 13:48:47

igor1982, please use [ code ] tags instead of [ quote ] for such listings. This makes them shorter, scrollable and easier to read.
See https://bbs.archlinux.org/help.php#bbcode

igor1982 · 2011-08-26 14:42:35

Thanks for your kindly reminding:)

bernarcher wrote:

igor1982, please use [ code ] tags instead of [ quote ] for such listings. This makes them shorter, scrollable and easier to read.
See https://bbs.archlinux.org/help.php#bbcode

pigiron · 2011-08-26 17:32:17

I just guess that it is a problem associated with unnormal shutdown procedure.

Well... if my guess is correct, then there are other reasons you may see that message.

Most Linux filesystems have a maximum mount count and/or a maximum date interval configured inside them. When you exceed the maximum(s), they'll start complaining; trying to tell us humans that we should run fsck on the filesystem.

If you want to display the maximums on that ext4 filesystem, then run tune2fs -l /dev/sdXY with root authority, where "X" and "Y" match the filesystem in question. Look for Maximum mount count: and Check interval:. You can use that same tune2fs command to change those values, but read the man page first.

Since I've never run a reiser filesystem, I don't know how to display it's values, but if you look at the "-c" and "-m" parameters in the reiserfstune man page, it will show you how to change those maximums.

Now... since most filesystems don't like to be fsck'd while mounted (at least in read/write mode), I'd highly suggest that you become familiar with "The sixth field" portion of the fstab man page. If you set your fstab file correctly, it will "Do The Right Thing" when it comes time to scan your filesystems during a boot.

(Edited to add:)

Oh...forgot to mention... those kernel logs entries are from your Intel wireless adapter device driver, not your filesystems

Last edited by pigiron (2011-08-26 17:43:54)

Arch Linux

#1 2011-08-26 12:34:54

Something about "filesystems is NOT Clean"

#2 2011-08-26 13:48:47

Re: Something about "filesystems is NOT Clean"

#3 2011-08-26 14:42:35

Re: Something about "filesystems is NOT Clean"

#4 2011-08-26 17:32:17

Re: Something about "filesystems is NOT Clean"

Board footer