From: L A Walsh <cifs-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
To: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: weirdness with cifsd
Date: Thu, 12 Jan 2017 15:49:12 -0800 [thread overview]
Message-ID: <587815F8.5050309@tlinx.org> (raw)
Just today, for the first time in a while, I have my Win machine
mounted on my linux machine.
But after a short while I'm seeing a large amount of read & write
network traffic between the two machines.
If I unmount the share (essentially my entire
Win disk), it stops. But otherwise, I see cifsd getting
100% of a cpu most of the time.
Is there a log like samba has to see what is being accessed?
I'm not sure at this point what is causing it...
(sorry for partial note before. I swear I clicked on save, but
must have hit send... (lame!)...
next reply other threads:[~2017-01-12 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 23:49 L A Walsh [this message]
[not found] ` <587815F8.5050309-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
2017-01-12 23:58 ` weirdness with cifsd Steve French
-- strict thread matches above, loose matches on Subject: below --
2017-01-12 23:46 L A Walsh
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=587815F8.5050309@tlinx.org \
--to=cifs-gt3auasyrbtytjvyw6ydsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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