Mdthbs

You look catfish vs You look like a catfish?

Why is Thanos so tough at the beginning of "Avengers: Endgame"?

How long can a 35mm film be used/stored before it starts to lose its quality after expiry?

Disabling Resource Governor in SQL Server

Who died in the Game of Thrones episode, "The Long Night"?

Public Salesforce Site and Security Review

Feels like I am getting dragged into office politics

Is Cola "probably the best-known" Latin word in the world? If not, which might it be?

How to reply this mail from potential PhD professor?

How to avoid grep command finding commented out strings in the source file?

What was the state of the German rail system in 1944?

Accidentally deleted the "/usr/share" folder

A non-technological, repeating, phenomenon in the sky, holding its position in the sky for hours

Hang 20lb projector screen on Hardieplank

Pressure to defend the relevance of one's area of mathematics

How to creep the reader out with what seems like a normal person?

Copy line and insert it in a new position with sed or awk

How to get SEEK accessing converted ID via view

Any examples of headwear for races with animal ears?

Has any spacecraft ever had the ability to directly communicate with civilian air traffic control?

Is balancing necessary on a full-wheel change?

Is this homebrew race based on the Draco Volans lizard species balanced?

Was the ancestor of SCSI, the SASI protocol, nothing more than a draft?

What word means "to make something obsolete"?

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system

Can I restart systemd without rebooting?tmpfs /run/user/1000 ran out of inodes, but it only has 30 filesUbuntu: Immovable .tmp file on network drive with no PIDCan't mount remote file system with sshfslsof - age of file“lsof: can't read namelist from /dev/ksyms” on Solarislsof - debug the output informationWhat exactly is a file offset in lsof output?How does `lsof` keep track of open file descriptors' filenames?understanding lsof during long operation on big file“stat -f” says “Type: fuseblk”. It should be “Type: fuse”Why can't unprivileged users nest FUSE mounts, but they can mount FUSE inside NFS with root_squash?Why can't `lsof` report some open port's information?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

21

7

What exactly is happening here?

root@bob-p7-1298c:/# ls -l /tmp/report.csv && lsof | grep "report.csv"

-rw-r--r-- 1 mysql mysql 1430 Dec  4 12:34 /tmp/report.csv

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs

      Output information may be incomplete.

privileges lsof fuse

share|improve this question

edited Dec 4 '14 at 23:45

Gilles

550k13111211636

asked Dec 4 '14 at 18:53

jmunschjmunsch

1,87411022

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are you getting this warning when you issue only lsof (without the | and grep)?
  
  – Sree
  Dec 4 '14 at 19:00
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The same warning occurs either way, but just lsof outputs a large list of the open files. I think it is a side issue. I thought that maybe the file was held open by a process and that might have been the reason why root was unable to move the file, but that doesn't appear to be the case. Hence the confusion.
  
  – jmunsch
  Dec 4 '14 at 19:03
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  yeah, looks like the can't stat... is another issue. I assume the real problem is the No such file or directory error that you are getting. This might sound idiotic, but does the location /home/bob/Desktop exist?
  
  – Sree
  Dec 4 '14 at 19:14
  

  
  
  
  

add a comment | 

21

7

What exactly is happening here?

root@bob-p7-1298c:/# ls -l /tmp/report.csv && lsof | grep "report.csv"

-rw-r--r-- 1 mysql mysql 1430 Dec  4 12:34 /tmp/report.csv

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs

      Output information may be incomplete.

privileges lsof fuse

share|improve this question

edited Dec 4 '14 at 23:45

Gilles

550k13111211636

asked Dec 4 '14 at 18:53

jmunschjmunsch

1,87411022

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are you getting this warning when you issue only lsof (without the | and grep)?
  
  – Sree
  Dec 4 '14 at 19:00
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The same warning occurs either way, but just lsof outputs a large list of the open files. I think it is a side issue. I thought that maybe the file was held open by a process and that might have been the reason why root was unable to move the file, but that doesn't appear to be the case. Hence the confusion.
  
  – jmunsch
  Dec 4 '14 at 19:03
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  yeah, looks like the can't stat... is another issue. I assume the real problem is the No such file or directory error that you are getting. This might sound idiotic, but does the location /home/bob/Desktop exist?
  
  – Sree
  Dec 4 '14 at 19:14
  

  
  
  
  

add a comment | 

What exactly is happening here?

root@bob-p7-1298c:/# ls -l /tmp/report.csv && lsof | grep "report.csv"

-rw-r--r-- 1 mysql mysql 1430 Dec  4 12:34 /tmp/report.csv

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs

      Output information may be incomplete.

privileges lsof fuse

share|improve this question

edited Dec 4 '14 at 23:45

Gilles

550k13111211636

asked Dec 4 '14 at 18:53

jmunschjmunsch

1,87411022

root@bob-p7-1298c:/# ls -l /tmp/report.csv && lsof | grep "report.csv"

-rw-r--r-- 1 mysql mysql 1430 Dec  4 12:34 /tmp/report.csv

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs

      Output information may be incomplete.

share|improve this question

edited Dec 4 '14 at 23:45

Gilles

550k13111211636

asked Dec 4 '14 at 18:53

jmunschjmunsch

1,87411022

share|improve this question

edited Dec 4 '14 at 23:45

Gilles

550k13111211636

asked Dec 4 '14 at 18:53

jmunschjmunsch

1,87411022

edited Dec 4 '14 at 23:45

Gilles

550k13111211636

edited Dec 4 '14 at 23:45

Gilles

550k13111211636

asked Dec 4 '14 at 18:53

jmunschjmunsch

1,87411022

asked Dec 4 '14 at 18:53

jmunschjmunsch

1,87411022

2 Answers
2

active

oldest

votes

28

FUSE and its access rights

lsof by default checks all mounted file systems including FUSE - file systems implemented in user space which have special access rights in Linux.

As you can see in this answer on Ask Ubuntu a mounted GVFS file system (special case of FUSE) is normally accessible only to the user which mounted it (the owner of gvfsd-fuse). Even root cannot access it. To override this restriction it is possible to use mount options allow_root and allow_other. The option must be also enabled in the FUSE daemon which is described for example in this answer ...but in your case you do not need to (and should not) change the access rights.

Excluding file systems from lsof

In your case lsof does not need to check the GVFS file systems so you can exclude the stat() calls on them using the -e option (or you can just ignore the waring):

lsof -e /run/user/1000/gvfs

Checking certain files by lsof

You are using lsof to get information about all processes running on your system and only then you filter the complete output using grep. If you want to check just certain files and the related processes use the -f option without a value directly following it then specify a list of files after the "end of options" separator --. This will be considerably faster.

lsof -e /run/user/1000/gvfs -f -- /tmp/report.csv

General solution

To exclude all mounted file systems on which stat() fails you can run something like this (in bash):

x=(); for a in $(mount | cut -d' ' -f3); do test -e "$a" || x+=("-e$a"); done

lsof "${x[@]}" -f -- /tmp/report.csv

Or to be sure to use stat() (test -e could be implemented a different way):

x=(); for a in $(mount | cut -d' ' -f3); do stat --printf= "$a" 2>/dev/null || x+=("-e$a"); done

share|improve this answer

edited Apr 13 '17 at 12:22

Community♦

1

answered Dec 4 '14 at 19:45

paboukpabouk

1,6251724

add a comment | 

11

lsof always tries to obtain some basic information about all filesystems, even if the arguments happen to imply that no result will come from a particular filesystem. If it's unable to access a filesystem (specifically, to call stat at its mount point, as the message says), it complains.

As root, you would normally have permission to access filesystems. However, due to the inner workings of FUSE, root does not automatically have all powers on a FUSE filesystem. This isn't a security feature (root can become the user who owns the filesystem and get access that way), it's a technical limitation.

GVFS-FUSE is a FUSE interface to GVFS, which is a mechanism that allows Gnome applications to access virtual filesystems implemented by Gnome plugins: GVFS grants non-Gnome applications access to these virtual filesystems via the regular filesystem interface.

share|improve this answer

answered Dec 5 '14 at 1:24

GillesGilles

550k13111211636

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f171519%2flsof-warning-cant-stat-fuse-gvfsd-fuse-file-system%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

28

FUSE and its access rights

lsof by default checks all mounted file systems including FUSE - file systems implemented in user space which have special access rights in Linux.

As you can see in this answer on Ask Ubuntu a mounted GVFS file system (special case of FUSE) is normally accessible only to the user which mounted it (the owner of gvfsd-fuse). Even root cannot access it. To override this restriction it is possible to use mount options allow_root and allow_other. The option must be also enabled in the FUSE daemon which is described for example in this answer ...but in your case you do not need to (and should not) change the access rights.

Excluding file systems from lsof

In your case lsof does not need to check the GVFS file systems so you can exclude the stat() calls on them using the -e option (or you can just ignore the waring):

lsof -e /run/user/1000/gvfs

Checking certain files by lsof

You are using lsof to get information about all processes running on your system and only then you filter the complete output using grep. If you want to check just certain files and the related processes use the -f option without a value directly following it then specify a list of files after the "end of options" separator --. This will be considerably faster.

lsof -e /run/user/1000/gvfs -f -- /tmp/report.csv

General solution

To exclude all mounted file systems on which stat() fails you can run something like this (in bash):

x=(); for a in $(mount | cut -d' ' -f3); do test -e "$a" || x+=("-e$a"); done

lsof "${x[@]}" -f -- /tmp/report.csv

Or to be sure to use stat() (test -e could be implemented a different way):

x=(); for a in $(mount | cut -d' ' -f3); do stat --printf= "$a" 2>/dev/null || x+=("-e$a"); done

share|improve this answer

edited Apr 13 '17 at 12:22

Community♦

1

answered Dec 4 '14 at 19:45

paboukpabouk

1,6251724

add a comment | 

28

FUSE and its access rights

lsof by default checks all mounted file systems including FUSE - file systems implemented in user space which have special access rights in Linux.

As you can see in this answer on Ask Ubuntu a mounted GVFS file system (special case of FUSE) is normally accessible only to the user which mounted it (the owner of gvfsd-fuse). Even root cannot access it. To override this restriction it is possible to use mount options allow_root and allow_other. The option must be also enabled in the FUSE daemon which is described for example in this answer ...but in your case you do not need to (and should not) change the access rights.

Excluding file systems from lsof

In your case lsof does not need to check the GVFS file systems so you can exclude the stat() calls on them using the -e option (or you can just ignore the waring):

lsof -e /run/user/1000/gvfs

Checking certain files by lsof

You are using lsof to get information about all processes running on your system and only then you filter the complete output using grep. If you want to check just certain files and the related processes use the -f option without a value directly following it then specify a list of files after the "end of options" separator --. This will be considerably faster.

lsof -e /run/user/1000/gvfs -f -- /tmp/report.csv

General solution

To exclude all mounted file systems on which stat() fails you can run something like this (in bash):

x=(); for a in $(mount | cut -d' ' -f3); do test -e "$a" || x+=("-e$a"); done

lsof "${x[@]}" -f -- /tmp/report.csv

Or to be sure to use stat() (test -e could be implemented a different way):

x=(); for a in $(mount | cut -d' ' -f3); do stat --printf= "$a" 2>/dev/null || x+=("-e$a"); done

share|improve this answer

edited Apr 13 '17 at 12:22

Community♦

1

answered Dec 4 '14 at 19:45

paboukpabouk

1,6251724

add a comment | 

FUSE and its access rights

lsof by default checks all mounted file systems including FUSE - file systems implemented in user space which have special access rights in Linux.

As you can see in this answer on Ask Ubuntu a mounted GVFS file system (special case of FUSE) is normally accessible only to the user which mounted it (the owner of gvfsd-fuse). Even root cannot access it. To override this restriction it is possible to use mount options allow_root and allow_other. The option must be also enabled in the FUSE daemon which is described for example in this answer ...but in your case you do not need to (and should not) change the access rights.

Excluding file systems from lsof

In your case lsof does not need to check the GVFS file systems so you can exclude the stat() calls on them using the -e option (or you can just ignore the waring):

lsof -e /run/user/1000/gvfs

Checking certain files by lsof

You are using lsof to get information about all processes running on your system and only then you filter the complete output using grep. If you want to check just certain files and the related processes use the -f option without a value directly following it then specify a list of files after the "end of options" separator --. This will be considerably faster.

lsof -e /run/user/1000/gvfs -f -- /tmp/report.csv

General solution

To exclude all mounted file systems on which stat() fails you can run something like this (in bash):

x=(); for a in $(mount | cut -d' ' -f3); do test -e "$a" || x+=("-e$a"); done

lsof "${x[@]}" -f -- /tmp/report.csv

Or to be sure to use stat() (test -e could be implemented a different way):

x=(); for a in $(mount | cut -d' ' -f3); do stat --printf= "$a" 2>/dev/null || x+=("-e$a"); done

share|improve this answer

edited Apr 13 '17 at 12:22

Community♦

1

answered Dec 4 '14 at 19:45

paboukpabouk

1,6251724

lsof -e /run/user/1000/gvfs

lsof -e /run/user/1000/gvfs -f -- /tmp/report.csv

x=(); for a in $(mount | cut -d' ' -f3); do test -e "$a" || x+=("-e$a"); done

lsof "${x[@]}" -f -- /tmp/report.csv

x=(); for a in $(mount | cut -d' ' -f3); do stat --printf= "$a" 2>/dev/null || x+=("-e$a"); done

share|improve this answer

edited Apr 13 '17 at 12:22

Community♦

1

answered Dec 4 '14 at 19:45

paboukpabouk

1,6251724

edited Apr 13 '17 at 12:22

Community♦

1

edited Apr 13 '17 at 12:22

Community♦

1

answered Dec 4 '14 at 19:45

paboukpabouk

1,6251724

answered Dec 4 '14 at 19:45

paboukpabouk

1,6251724

11

lsof always tries to obtain some basic information about all filesystems, even if the arguments happen to imply that no result will come from a particular filesystem. If it's unable to access a filesystem (specifically, to call stat at its mount point, as the message says), it complains.

As root, you would normally have permission to access filesystems. However, due to the inner workings of FUSE, root does not automatically have all powers on a FUSE filesystem. This isn't a security feature (root can become the user who owns the filesystem and get access that way), it's a technical limitation.

GVFS-FUSE is a FUSE interface to GVFS, which is a mechanism that allows Gnome applications to access virtual filesystems implemented by Gnome plugins: GVFS grants non-Gnome applications access to these virtual filesystems via the regular filesystem interface.

share|improve this answer

answered Dec 5 '14 at 1:24

GillesGilles

550k13111211636

add a comment | 

11

lsof always tries to obtain some basic information about all filesystems, even if the arguments happen to imply that no result will come from a particular filesystem. If it's unable to access a filesystem (specifically, to call stat at its mount point, as the message says), it complains.

As root, you would normally have permission to access filesystems. However, due to the inner workings of FUSE, root does not automatically have all powers on a FUSE filesystem. This isn't a security feature (root can become the user who owns the filesystem and get access that way), it's a technical limitation.

GVFS-FUSE is a FUSE interface to GVFS, which is a mechanism that allows Gnome applications to access virtual filesystems implemented by Gnome plugins: GVFS grants non-Gnome applications access to these virtual filesystems via the regular filesystem interface.

share|improve this answer

answered Dec 5 '14 at 1:24

GillesGilles

550k13111211636

add a comment | 

lsof always tries to obtain some basic information about all filesystems, even if the arguments happen to imply that no result will come from a particular filesystem. If it's unable to access a filesystem (specifically, to call stat at its mount point, as the message says), it complains.

As root, you would normally have permission to access filesystems. However, due to the inner workings of FUSE, root does not automatically have all powers on a FUSE filesystem. This isn't a security feature (root can become the user who owns the filesystem and get access that way), it's a technical limitation.

GVFS-FUSE is a FUSE interface to GVFS, which is a mechanism that allows Gnome applications to access virtual filesystems implemented by Gnome plugins: GVFS grants non-Gnome applications access to these virtual filesystems via the regular filesystem interface.

share|improve this answer

answered Dec 5 '14 at 1:24

GillesGilles

550k13111211636

share|improve this answer

answered Dec 5 '14 at 1:24

GillesGilles

550k13111211636

answered Dec 5 '14 at 1:24

GillesGilles

550k13111211636

answered Dec 5 '14 at 1:24

GillesGilles

550k13111211636