My /var/log/messages reports…
Feb 6 07:59:36 apollo systemd-tmpfile[3428]: stat(/run/user/ion/gvfs) failed: Permission denied
/run/user/ion/gvfs is a directory with nothing in it. It readable by the user. What is systemd trying to do and failing?
Thanks in advance for any explanation.
So gvfs is a GNOME thing. You can read about it here: GVFS - Wikipedia, the free encyclopedia, I see bug reports, but not in our bugzilla, about root not being able to stat ~/.gvfs, which may be used by some backup software. Using STAT means - to display file or file system status. You are the user called ion I guess. I feel like a fortune teller trying to make sense of this little bit of an error message. So, its about your user area /home/ion perhaps, you use GNOME and openSUSE 12.2 (or maybe 12.1) with systemd and perhaps you are trying to backup your home area and there may be a bug where root is trying to stat ~/.gvfs and it does not work. Does this sound like you?
Thank You,
This isn’t actually an explanation. My logfile contains:
Feb 4 12:04:06 nwr2 systemd-tmpfile[10585]: stat(/run/user/rickert/gvfs) failed: Permission denied
Feb 5 12:04:05 nwr2 systemd-tmpfile[30978]: stat(/run/user/rickert/gvfs) failed: Permission denied
Feb 6 12:04:04 nwr2 systemd-tmpfile[21702]: stat(/run/user/rickert/gvfs) failed: Permission denied
and earlier similar messages.
The first of those might have been a boot time message. The others were not.
At present “/run/user/rickert” is empty. I am not aware of running anything that would result in a “gvfs” mount.
On 02/06/2013 11:26 PM, ionmich wrote:
>
> stat(/run/user/ion/gvfs) failed: Permission denied
https://www.google.com/search?q=gvfs+Permission+denied
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
Sorry, I should have made my signature more prominent as it shows…
openSUSE 12.2 64bit KDE Version 4.8.5 (4.8.5) "release 2"
…so no, I don’t use GNOME. Furthermore I have come to accept ~/.gvfs errors as every “rsync” backup I perform returns one. What I don’t understand is why my bootup is delayed over an empty directory needed by a GUI I don’t use.
Thanks for the response. I did find those links with Google before I posted here, but neither the Ubuntu nor the Archlinux links led to any answers to my query. However since you took the time to research them, I will read them again in case I missed something.
On 02/07/2013 04:36 PM, ionmich wrote:
> so no, I don’t use GNOME.
if you install any gnome applications they will have some dependencies
that must also be installed…
apparently gvfs is installed in that case–i say, because i see i have a
gvfs also (i can’t remember which gnome app i installed, but i’m sure i did)
> Furthermore I have come to accept ~/.gvfs
> errors as every “rsync” backup I perform returns one.
try using in your command line magic
--exclude=*.gvfs
you may have to provide the full path instead of the wild card
> What I don’t understand is why my bootup is delayed over an empty directory needed by
> a GUI I don’t use.
i have not noticed any boot slowdown caused by gvfs…how much are you
seeing…
it may be that gvfs should not be installed/mounted for every/any gnome
application…maybe there should be a bug logged ??
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
On 02/07/2013 04:46 PM, ionmich wrote:
> However since you took the time to research them, I
> will read them again in case I missed something.
there may not be a direct answer to your specific questions…but, i
have just started an experiment: i have removed .gvfs from my home’s
root directory, and so far (10 minutes) i have found no ill effects…
i would expect to have problems only if using .gvfs to interact with
distant file systems, automatically…or possibly some gnome
applications might touch it…i do not know…
READ the caveat in my sig before following any of:
my machine may catch on fire tomorrow, but what i did in a user konsole was:
sudo umount /home/[username]/.gvfs
mkdir /home/[username]/archive
mv /home/[username]/.gvfs /home/[username]/archive/.gvfs
that will first unmount gvfs (must be done prior to move/delete), then
make an “archive” directory (or name it whatever you want) to store it,
and finally move gvfs…
why move it, because i do not know the long term effects…maybe i need
to move it back…if i see errors or strangeness involving gvfs i would
boot to runlevel 3 and log in as my user, then
mv /home/[username]/archive/.gvfs /home/[username]/.gvfs
su -
mount /home/[username]/.gvfs
init 5
note, even if you move it to /archive if you rsync the entire /home you
will see the error again if you do not exclude…
Thank you VERY much for your highly informative responses. My boot time delay is 12 seconds. I will report back with whatever results I get.
Once again I have confused myself, and others. I connected the boot error…
Feb 6 07:59:36 apollo systemd-tmpfile[3428]: stat(/run/user/ion/gvfs) failed: Permission denied
…note “/gvfs” not “/.gvfs” , dot missing, with the rsync no permission error writing to /home/ion/.gvfs
Two different observations. Sorry, sorry, sorry.
This makes sense.
try using in your command line magic
–exclude=*.gvfs
This also works.
I have also moved .gvfs from my home directory to a safe place and rebooted several times with no ill effects so far. I suspect that as you mentioned if I run any GNOME based software it will re-appear. But as I don’t know which of the applications I use depend on GNOME files it will take some time to test.
When I set the permissions on this directory to be writeable by the owner, the very next boot removed the directory altogether, and there was no error reported. Also boot time was faster. But then on the next boot, the directory re-appeared with read-only permission and the whole initial process repeated. Puzzling.
The log messages (the “tmpfile” string) indicate that this is part of a cleanup of temporary files. The directory “/run/user” is one of the directories configured for such cleanup.
I’m guessing that the cleanup process takes this error in its stride, and that it doesn’t actually cause a time delay beyond a millisecond or two.
On 2013-02-07 22:46, ionmich wrote:
> I have also moved .gvfs from my home directory to a safe place and
> rebooted several times with no ill effects so far.
If you login text mode instead of graphical mode, you can simply erase
that directory, it is dynamically created when needed.
However, the “/run/user/*/gvfs” file is new to me. I don’t run 12.2 so I
don’t even have the /run directory. It must be some kind of flag.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-02-07 23:16, ionmich wrote:
>
> ionmich;2525123 Wrote:
>> /run/user/ion/gvfs is a directory with nothing in it. It readable by
>> the user. What is systemd trying to do and failing?
>>
>
> When I set the permissions on this directory to be writeable by the
> owner, the very next boot removed the directory altogether, and there
> was no error reported. Also boot time was faster. But then on the next
> boot, the directory re-appeared with read-only permission and the whole
> initial process repeated. Puzzling.
The “/run” directory is dynamic. It does not exist in disk, but in
memory, and thus any change you do there is not permanent.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I think it has just moved there, from “$HOME/.gvfs”. I am no longer seeing “$HOME/.gvfs” created.
On 2013-02-08 00:56, nrickert wrote:
>
> robin_listas;2525384 Wrote:
>> However, the “/run/user/*/gvfs” file is new to me. I don’t run 12.2 so I
>> don’t even have the /run directory.
>
> I think it has just moved there, from “$HOME/.gvfs”. I am no longer
> seeing “$HOME/.gvfs” created.
Good idea.
We can then make a backup of home without the nuisance from that
directory failing permissions, and we do not need a backup of /run.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I agree.
In 12.3, it is instead at “/run/user/1001/gvfs”
and note that 1001 is my uid. I suppose that’s because two different users could share the same uid, so they should share the same gvfs.
Also, in 12.3, if I plug in a USB and mount it in KDE, then it shows up in “/run/media/rickert/label-or-uuid-of-disk”. I’m not sure why they used the userid rather than the uid there. It seems a tad inconsistent.
And I guess I have gone way off-topic for this thread.
On 02/07/2013 10:46 PM, ionmich wrote:
> I have also moved .gvfs from my home directory
sigh! i see it has magically reappeared in my home…
and, i have no /run in my root…strange that you do. it is sure not
from the old days…sounds like something some Ship Jumper thought
would be a new, good idea!
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
On 2013-02-08 07:48, dd wrote:
> On 02/07/2013 10:46 PM, ionmich wrote:
>> I have also moved .gvfs from my home directory
>
> sigh! i see it has magically reappeared in my home…
Yes, as soon as some gnome app runs. You might find out which with an
apparmour rule that forbids that directory. Let me see… The trick was
mentioned by Cristian Rodríguez in 2009, and you have to modify it as
needed:
+++······················
try this:
and then watch the logs…
if auditctl is not found, when you execute it as root, install package
“audit”
······················+±
At the time, some unknown process was removing permissions of /dev/null.
> and, i have no /run in my root…strange that you do.
Not strange, it was introduced with 12.2, a sysmted feature or requisite.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)