I have a directory in my home directory named .gvfs with the following
properties when I do an ls -Al:
d????????? ? ? ? ? ? .gvfs
I can't access it, delete it, nor rename it; nor can root do any of
those things. I keep getting error messages in the terminal saying as
such, too. Does anybody know how I can fix this?
The way that you wrote this Gene I would think that your "driving amanda
to squawk" problem is an amanda problem not a .gvfs problem. Amanda is
an 'addon' backup application, correct? And .gvfs is part of the Fedora
operating file system. This .gvfs *belongs* there and is needed.
By what, David? I'm running kde here. I just made that script from a
previous message, then did a killall on the daemon, and with that gone the
tree if any has now been deleted. We will wait and see what squawks.
As far as the comment about an addon, non-approved app like amanda is
concerned, I have been running amanda since back in the day when redhat
actually supplied bru as its backup app. Amanda beat it then, and still beats
anything in the fedora repos 11 years later. Quality code generally stands
the test of time, particularly when it has been in active development for all
of those years, even before linux itself I believe as its an even older unix
app. I'm running the snapshot taken on 06/22/2009 right now. Where is bru
today? I have no idea.
As far as I can see, there is no distinction between gnome-vfs2 and
amanda in terms of what is an 'addon'. They both come from the same
repositories. Gnome is the certainly a default in some Fedora spins,
but that doesn't make it and it's dependencies the one-true-desktop.
I like gnome-vfs2, I use it a lot - but I'm a Gnome user - I can quite
see why KIOSlave would be more important to KDE users and other
methods of accessing virtual filesystems important to other DE users.
If Gene doesn't want gvfs, then it shouldn't be there - Free Operating
systems are about empowering user choice!
But that said, I get the same thing with my .gvfs directory when I ssh
in to a freshly booted system without Gnome running - which may be the
environment that amanda might have to deal with - and having screwy
permissions at any point has to rate a bug surely?
Sorry Sam, not true for me. The things that are done to amanda in order to
hammer it into the rpm mold do not set well with amanda's security model. So
the amanda here is built from their tarball, and has been so for over a
decade.
Amen. There are things in the std kernel that I never build, device-mapper
being one of them. They started playing with the drive ordering about 3 years
ago, and the only way I can protect myself from the volatility of that is to
not enable it at all, so /dev/sda _stays_ /dev/sda without becoming /dev/sdh
the next time I boot. That obviously is a boot failure that requires I play
with the (hd0,0) statements in my grub.conf until I find the magic twanger
that will work, more than likely only for that particular bootup. I have I
think, 4 stanza's of fedora kernels in my grub.conf, with all files needed in
the /boot partition. I actually tried to boot one of them about 4 months
back, and it couldn't find and mount /, device mapper was enabled I guess.
But its there, right on /dev/sda3, exactly where I put it, and exactly where
my grub.conf says it is.
So when it happened and I fussed, I got laughed at & told to 'get used to it'.
Sorry, such BS just doesn't cut it. My pleas for stable device mapping were
thrown under the bus & the driver slapped cuz the bus wasn't moving quickly
enough. I look at the bootup fussing that it can't find device-mapper every
boot, BUT IT BOOTS...
When I said addon I meant 'no part of the original installed operating
system'. And I would still be more inclined to pester the amanda
developers about this bug than to perhaps disable a perfectly running
computer.
That depends on whose fault it is. Having something existing on a system that
not even root can control sends up alarms, fireworks and red flags to me.
There is no way in hell I can lay that problem on amanda's doorstep. This is
supposed to be open source, where everything is visible and controllable.
This thing seems to have been under the radar till it just showed up, set as a
default someplace.
As for starting something called FUSE at boot time, should not whatever it is
that starts the daemon set off a fuss if it cannot find the daemon to start
it? I just rebooted, to 2.6.30.1 because the oom killer in 31-rc2 only allows
around 12-18 hours of uptime, BIG memory leak somewhere. And no mention shows
in a dmesg, I just looked again.
If quoting a thread, then IMNSHO the thread should have the definitive answer.
And that thread never gets to an answer. Not being a gnome user, if it is
part of gnome, and I'm not running gnome (spit), then why can't it be un-
mounted or deleted? All those answers are dbl-talk to me.
Here it claims it is busy. And I get an email from amanda every morning
claiming it cannot access it.
So how about answering the original question?, which seemed to be something
along the lines of a 'how can I get rid of it' question.
The point is now moot I believe, although I haven't checked since a reboot was
forced by kernel-2.6.31-rc2's oom killer just now. So I'm back on 2.6.30.1 &
its doofy clock.
Have you tried unmounting it? I'm not a Gnome user either, and I
unmounted it with no trouble. I did have to do it as root, but with an
appropriate fstab entry that would presumably not be necessary. I
haven't bothered because it doesn't get in my way.
I don't know how to get rid of it (I wish I did), but I do
know it isn't a "real" directory. It is some imaginary
nonsense gnome created to produce some kind of virtual
filesystem (using fuse I think) which the gnome developers
imagine is useful, but is (like so much else in gnome)
really just a pain that causes untold problems in many
different tools.
I'm already using as little of gnome as I possibly can, yet something starts
the damn gvfs daemon in the microscopic parts of gnome I am
forced to start to get any gtk app to work at all :-).
Maybe if I created a plain file named ~/.gvfs and did a chattr +i on
it that would frustrate the daemon enough to leave me alone - I'll
have to try it sometime...
OK, I finally took the time to discover a way to squash it utterly.
I now have my system setup to run this script after ever yum
update (so if it comes back, I'll squash it again):
#!/bin/bash
#
if [ -f /usr/libexec/gvfs-fuse-daemon ]
then
rm -f /usr/libexec/NOTgvfs-fuse-daemonNOT
mv /usr/libexec/gvfs-fuse-daemon /usr/libexec/NOTgvfs-fuse-daemonNOT
fi
By renaming the daemon that runs the fuse mount, it can't
get it started.
I haven't noticed a single thing that fails to function
yet with it disabled like this.
I can't just remove the package that provides the daemon because
several things claim to depend on it, but despite that, they
all seem to work fine without it running.
My ~/.gvfs directory is now just a plain directory with no
weird attributes to confuse the heck out of backup
programs, etc.
I'm betting it is hard coded in gnome-settings-daemon since that is
about the only thing from gnome I always start, but they could
have hid it somewhere else too. If you are really bored you could
try running "strings -a" on all the programs installed by any
gnome packages and see which one has the string "gvfs-fuse-daemon"
in it :-). I already tried searching the gconf database and
it doesn't appear in there anywhere that I can find.
Re: Help with d????????? ? ? ? ? ? .gvfs
I'll follow this thread too, as I have it, and its driving amanda to squawk
about it. And root cannot do anything to it either.
Re: Help with d????????? ? ? ? ? ? .gvfs
The way that you wrote this Gene I would think that your "driving amanda
to squawk" problem is an amanda problem not a .gvfs problem. Amanda is
an 'addon' backup application, correct? And .gvfs is part of the Fedora
operating file system. This .gvfs *belongs* there and is needed.
Re: Help with d????????? ? ? ? ? ? .gvfs
By what, David? I'm running kde here. I just made that script from a
previous message, then did a killall on the daemon, and with that gone the
tree if any has now been deleted. We will wait and see what squawks.
As far as the comment about an addon, non-approved app like amanda is
concerned, I have been running amanda since back in the day when redhat
actually supplied bru as its backup app. Amanda beat it then, and still beats
anything in the fedora repos 11 years later. Quality code generally stands
the test of time, particularly when it has been in active development for all
of those years, even before linux itself I believe as its an even older unix
app. I'm running the snapshot taken on 06/22/2009 right now. Where is bru
today? I have no idea.
Re: Help with d????????? ? ? ? ? ? .gvfs
2009/7/6 Gene Heskett :
As far as I can see, there is no distinction between gnome-vfs2 and
amanda in terms of what is an 'addon'. They both come from the same
repositories. Gnome is the certainly a default in some Fedora spins,
but that doesn't make it and it's dependencies the one-true-desktop.
I like gnome-vfs2, I use it a lot - but I'm a Gnome user - I can quite
see why KIOSlave would be more important to KDE users and other
methods of accessing virtual filesystems important to other DE users.
If Gene doesn't want gvfs, then it shouldn't be there - Free Operating
systems are about empowering user choice!
But that said, I get the same thing with my .gvfs directory when I ssh
in to a freshly booted system without Gnome running - which may be the
environment that amanda might have to deal with - and having screwy
permissions at any point has to rate a bug surely?
Re: Help with d????????? ? ? ? ? ? .gvfs
[...]
Sorry Sam, not true for me. The things that are done to amanda in order to
hammer it into the rpm mold do not set well with amanda's security model. So
the amanda here is built from their tarball, and has been so for over a
decade.
Amen. There are things in the std kernel that I never build, device-mapper
being one of them. They started playing with the drive ordering about 3 years
ago, and the only way I can protect myself from the volatility of that is to
not enable it at all, so /dev/sda _stays_ /dev/sda without becoming /dev/sdh
the next time I boot. That obviously is a boot failure that requires I play
with the (hd0,0) statements in my grub.conf until I find the magic twanger
that will work, more than likely only for that particular bootup. I have I
think, 4 stanza's of fedora kernels in my grub.conf, with all files needed in
the /boot partition. I actually tried to boot one of them about 4 months
back, and it couldn't find and mount /, device mapper was enabled I guess.
But its there, right on /dev/sda3, exactly where I put it, and exactly where
my grub.conf says it is.
So when it happened and I fussed, I got laughed at & told to 'get used to it'.
Sorry, such BS just doesn't cut it. My pleas for stable device mapping were
thrown under the bus & the driver slapped cuz the bus wasn't moving quickly
enough. I look at the bootup fussing that it can't find device-mapper every
boot, BUT IT BOOTS...
I concur 100% that its a bug.
Re: Help with d????????? ? ? ? ? ? .gvfs
FUSE
Filesystem in Userspace
http://en.wikipedia.org/wiki/Filesystem_in_Userspace
My guess would be something important. :-)
When I said addon I meant 'no part of the original installed operating
system'. And I would still be more inclined to pester the amanda
developers about this bug than to perhaps disable a perfectly running
computer.
Re: Help with d????????? ? ? ? ? ? .gvfs
That depends on whose fault it is. Having something existing on a system that
not even root can control sends up alarms, fireworks and red flags to me.
There is no way in hell I can lay that problem on amanda's doorstep. This is
supposed to be open source, where everything is visible and controllable.
This thing seems to have been under the radar till it just showed up, set as a
default someplace.
As for starting something called FUSE at boot time, should not whatever it is
that starts the daemon set off a fuss if it cannot find the daemon to start
it? I just rebooted, to 2.6.30.1 because the oom killer in 31-rc2 only allows
around 12-18 hours of uptime, BIG memory leak somewhere. And no mention shows
in a dmesg, I just looked again.
Re: Help with d????????? ? ? ? ? ? .gvfs
"Just showed up"? Do you mean gvfs? It "just showed up" in the Fedora 9
release.
Good for you.
Re: Help with d????????? ? ? ? ? ? .gvfs
actually Gene Heskett
Which I never ran, going from F8 to F10.
Re: Help with d????????? ? ? ? ? ? .gvfs
This has been discussed at length already:
https://www.redhat.com/archives/fedora-list/2008-October/msg02751.html
poc
Re: Help with d????????? ? ? ? ? ? .gvfs
If quoting a thread, then IMNSHO the thread should have the definitive answer.
And that thread never gets to an answer. Not being a gnome user, if it is
part of gnome, and I'm not running gnome (spit), then why can't it be un-
mounted or deleted? All those answers are dbl-talk to me.
Here it claims it is busy. And I get an email from amanda every morning
claiming it cannot access it.
So how about answering the original question?, which seemed to be something
along the lines of a 'how can I get rid of it' question.
Re: Help with d????????? ? ? ? ? ? .gvfs
Then try a wider search:
http://markmail.org/search/list:com.redhat.fedora-list?q=gvfs#query:list
%3Acom.redhat.fedora-list%20gvfs+page:1+mid:zsyhw6ysrteazqz7
+state:results
And of course Google, as ever.
poc
Re: Help with d????????? ? ? ? ? ? .gvfs
The point is now moot I believe, although I haven't checked since a reboot was
forced by kernel-2.6.31-rc2's oom killer just now. So I'm back on 2.6.30.1 &
its doofy clock.
No, it was not re-created by the reboot.
Re: Help with d????????? ? ? ? ? ? .gvfs
Have you tried unmounting it? I'm not a Gnome user either, and I
unmounted it with no trouble. I did have to do it as root, but with an
appropriate fstab entry that would presumably not be necessary. I
haven't bothered because it doesn't get in my way.
poc
Re: Help with d????????? ? ? ? ? ? .gvfs
umount told root it was busy.
Re: Help with d????????? ? ? ? ? ? .gvfs
Which means something was using it, so maybe you do actually need it.
You could use 'lsof .gvfs' to find out more.
poc
Re: Help with d????????? ? ? ? ? ? .gvfs
William M. Quarles wrote, at 07/06/2009 08:32 PM +9:00:
I guess you are seeing this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=493565
Several people (including me) reported this issue, however no
one has found how to "reproduce" this exactly and no
solution is found yet.
Regards,
Mamoru
Re: Help with d????????? ? ? ? ? ? .gvfs
http://library.gnome.org/misc/release-notes/2.22/#sect:gvfs-gio
Re: Help with d????????? ? ? ? ? ? .gvfs
On Mon, 06 Jul 2009 07:32:07 -0400
I don't know how to get rid of it (I wish I did), but I do
know it isn't a "real" directory. It is some imaginary
nonsense gnome created to produce some kind of virtual
filesystem (using fuse I think) which the gnome developers
imagine is useful, but is (like so much else in gnome)
really just a pain that causes untold problems in many
different tools.
Re: Help with d????????? ? ? ? ? ? .gvfs
Re: Help with d????????? ? ? ? ? ? .gvfs
On Mon, 6 Jul 2009 13:43:29 +0000 (UTC)
I'm already using as little of gnome as I possibly can, yet something starts
the damn gvfs daemon in the microscopic parts of gnome I am
forced to start to get any gtk app to work at all :-).
Maybe if I created a plain file named ~/.gvfs and did a chattr +i on
it that would frustrate the daemon enough to leave me alone - I'll
have to try it sometime...
Re: Help with d????????? ? ? ? ? ? .gvfs
On Mon, 6 Jul 2009 09:51:43 -0400
OK, I finally took the time to discover a way to squash it utterly.
I now have my system setup to run this script after ever yum
update (so if it comes back, I'll squash it again):
#!/bin/bash
#
if [ -f /usr/libexec/gvfs-fuse-daemon ]
then
rm -f /usr/libexec/NOTgvfs-fuse-daemonNOT
mv /usr/libexec/gvfs-fuse-daemon /usr/libexec/NOTgvfs-fuse-daemonNOT
fi
By renaming the daemon that runs the fuse mount, it can't
get it started.
I haven't noticed a single thing that fails to function
yet with it disabled like this.
I can't just remove the package that provides the daemon because
several things claim to depend on it, but despite that, they
all seem to work fine without it running.
My ~/.gvfs directory is now just a plain directory with no
weird attributes to confuse the heck out of backup
programs, etc.
Re: Help with d????????? ? ? ? ? ? .gvfs
Thank you very much. Between that and a killall fuse, I can and have deleted
it. Now we wait to see what fusses.
What gets me is that there is no starter code anyplace in /etc/rc* that starts
it.
Re: Help with d????????? ? ? ? ? ? .gvfs
On Mon, 06 Jul 2009 17:18:17 -0400
I'm betting it is hard coded in gnome-settings-daemon since that is
about the only thing from gnome I always start, but they could
have hid it somewhere else too. If you are really bored you could
try running "strings -a" on all the programs installed by any
gnome packages and see which one has the string "gvfs-fuse-daemon"
in it :-). I already tried searching the gconf database and
it doesn't appear in there anywhere that I can find.
Re: Help with d????????? ? ? ? ? ? .gvfs
Re: Help with d????????? ? ? ? ? ? .gvfs
Yeah, I had to go into rescue mode with an installation disc and run
fsck, through which the problem was fixed. No deletion necessary!
Peace,
William