Tag Info

New answers tagged

0

Too fast diagnosis I read online that this might be resolved by repairing permission on the drive. Unfortunatly, from the description of your problem, this is wrong. What need to be repaired is the filesystem on your external disk SEAGATE. Analysis of lsof The output of your lsof command tells that the command mds (1st column) is actually reading ...


0

It appears that Spotlight is indexing this drive. There could be a problem that is causing Spotlight to hang up and constantly pound this drive. The mds process is the metadata server. Try killing this process and then tell spotlight to not index this drive. To disable spotlight indexing go to System Preferences -> Spotlight -> Privacy and add the disk to ...


4

On Linux at least, lsof can't tell you which end initiated the connection as it gets the list from /proc/net/tcp where that information is not available. The first address always refers to the local endpoint. Recent versions of the ss utility (which use a different kernel API to retrieve connection information), with -e, will give you direction but ...


4

I think the clue is in the port numbers, take these two entries smtpd 12950 postfix 9u IPv4 35762406 0t0 TCP hostname:smtp->spe.cif.ic.IP:55277 (ESTABLISHED) smtp 13007 postfix 13u IPv4 35762309 0t0 TCP hostname:34434->fake.VVVVV.fr:smtp (ESTABLISHED) smtpd has received a connection on port smtp(25) from a high port number, ...


3

The offset is the current position in the file, as maintained by the kernel for a given file descriptor (see the lseek(2) manpage for details). As to why it's useful in lsof's output, I'm not really sure. It can give some idea of a process's progress through a file, although it won't cover all cases (memory-mapped files won't show offset changes).



Top 50 recent answers are included