From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to find out to what file(...) writes goes on a idle system...
Date: Sat, 6 Dec 2014 14:19:08 +0300 [thread overview]
Message-ID: <20141206141908.b5550bb576d0936367d7765e@gentoo.org> (raw)
In-Reply-To: <87k325qbyb.fsf@inbox.lv>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Sat, 06 Dec 2014 12:01:16 +0100 Johannes Altmanninger wrote:
> Hi,
>
> meino.cramer@gmx.de writes:
>
> > In the context of preserving the live of flash media by minimizing
> > the count of unessary writes I want to know which
> > application/daemon/etc is continous writing to that media and which
> > """entity""" (file/pipe/fifo...) is receiving those writes...
>
> You could use this:
>
> # echo 1 > /proc/sys/vm/block_dump
>
> then every read and write operation on block devices shows up in dmesg
> with the PID, process name and the block id. (This can be a lot of
> lines, so dmesg -c might be useful) I'm not exactly sure how to identify
> which files belong to which block, though.
This depends on filesystem being used. For ext* family debugfs may
be used:
# debugfs /dev/<your_dev>
ncheck inode1 inode2 ...
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-06 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 6:56 [gentoo-user] How to find out to what file(...) writes goes on a idle system meino.cramer
2014-12-06 11:01 ` Johannes Altmanninger
2014-12-06 11:19 ` Andrew Savchenko [this message]
2014-12-06 11:27 ` lee
2014-12-06 14:16 ` Frank Steinmetzger
2014-12-06 17:11 ` [gentoo-user] " James
2014-12-06 19:04 ` meino.cramer
2014-12-06 20:14 ` James
2014-12-07 4:05 ` meino.cramer
2014-12-07 11:23 ` Tom H
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=20141206141908.b5550bb576d0936367d7765e@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-user@lists.gentoo.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