Re: Why this activity on mounted but unused fs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/11/18 6:39 pm, Berend De Schouwer wrote:
On Sun, 2018-11-04 at 17:32 +1100, Eyal Lebedinsky wrote:
On 4/11/18 4:44 pm, Samuel Sieb wrote:
On 11/3/18 10:19 PM, Eyal Lebedinsky wrote:
What is this io, and can it be stopped? I want to allow the disks
to enter
low power mode (not spin down) when idle.

I'm assuming since it's a new RAID that you haven't created files
on it yet, or at least not many.  Try running "lsof +D /mnt/point"
to see if there is any process looking at it.  Then try running
"inotifywait -rm /mnt/point" and let it run for a little while to
see if you can catch some process accessing the fs.  You will need
to install "inotify-tools" to get that program.

Sure, should have said a bit more: The array was resync'ed, then
(much) data was copied in. This was a few days ago.

Did the sync finish?  What is the kernel status of the array?
cat /proc/mdstat

Yes, as I mentioned, the sync finished (28/Oct), then the copy finished (30/Oct).
Acquired a new case and installed the array there (using an old mobo) testing how
the case ventilation performs. Waiting for a new mobo/CPU/mem.

It is during this quiet period that I noticed the io issue which got me wondering.

Since this happens only when the array is mounted, and I do not see any files being
touched, I wondered if this is some ext4 internal housekeeping. Can this be related
to the size of the fs?
	Filesystem      Size  Used Avail Use% Mounted on
	/dev/md127       55T   17T   38T  32% /new-raid

$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid6 sdc1[1] sdb1[0] sdf1[4] sdh1[6] sde1[3] sdd1[2] sdg1[5]
      58593761280 blocks super 1.2 level 6, 512k chunk, algorithm 2 [7/7] [UUUUUUU]
      bitmap: 1/88 pages [4KB], 65536KB chunk

unused devices: <none>

--
Eyal at Home (fedora@xxxxxxxxxxxxxx)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux