Daniel Benamy | 27 Aug 06:50
Picon
Gravatar

File system closing


I've got an odd problem. If I run my file system and use some
operations including open and readlink, it's fine. If I use my read
which is a special blocking call, it seems to works ok for maybe a
minute and the suddenly the file system closes. gdb says it's exiting
normally and I've run it with libgmalloc and it's not accessing
invalid memory. If I do the read and then nothing else it'll close
after a little while and if I do other things after the read (while
it's still blocked) they work until it exits. Any ideas about what
could cause this?
Thanks a lot,
Dan

Daniel Benamy | 26 Aug 03:49
Picon
Gravatar

Blocking requests


I've got a fuse file system which sometimes intentionally blocks
requests. It works with fuse on linux which spawns new threads for
each request and is happy to leave some hanging around for a while and
process other requests. But when I run it with macfuse, its acting as
though when one request blocks, the whole thing gets stuck. Is this
intentional? Is there any way around it? I did a bit of searching on
the web and skimmed the code and I haven't found anything about this.
Thanks a lot,
Dan
Elliott | 18 Aug 16:02
Picon

Group permissions weirdness


Not sure if this is the wrong place to ask.  My apologies if it is
not.

I mount a remote server over SSH using a specific user.  This user is
part of a group that has full access to certain files, but I am unable
to overwrite them.  If I change the files to be owned by this user, it
works fine.  If I directly SSH into the server as the user, I can
write to the files as well.  Files are set to 775.

Any suggestions?  Thank you!
Jeff Mancuso | 15 Aug 01:40
Picon
Gravatar

Volume ejection with volumes tagged as local


We mark all of our volumes as local because to make it easier for our
Leopard users to get to the mount. This obviously comes with some
complications, that is well noted in the docs, and we think we deal
with them pretty gracefully - all in all.

One lingering question I've been meaning to ask surrounds the unmount
behavior. When there are multiple FUSE volumes mounted that are tagged
with local and you click to eject one of them from Finder - the alert
dialog is opened asking if you want to eject all the volumes in this
particular device, or only one. In our situation, the answer is always
going to be only one.

Is it possible [at least theoretically] for each FUSE volume to be
somehow marked with a different device ID so that when a user attempts
to umount, this message isn't displayed? I understand if there are
potentially undesirable consequences from heading down this path, and
that the local flag is explicitly unsupported - but I thought I'd
bring it up and see if it was possible via a mount option or extension
in the future.

Thanks
-Jeff

Picon

ENXIO - Device not configured

Hi,
 I am seeing ENXIO error on mountpoint. I understand that it comes if
MacFuse detects few calls return -1, (mostly STATFS returning -1?). The
problem for me is that, as our's is network filesystem, there are cases when
the remote node can get disconnected. And I noticed that once the device
starts returning ENXIO (marked dead?), it doesn't send any calls to below
layer, even though after some time the remote node gets connected.

 The observation is that, 'stat' on mountpoint gives device not configured
error, 'df' gets proper output after remote brick gets connected.

 Any suggestions on how to solve this problem?

Regards,
Amar

--

-- 
Amar Tumballi
Gluster/GlusterFS Hacker
[bulde on #gluster/irc.gnu.org]
http://www.zresearch.com - Commoditizing Super Storage!

pgn | 13 Aug 06:43
Picon

sshfs fails to mount, error: "kernel[0]: MacFUSE: force ejecting (no response from user space 5)"


i've done a 1st install of MacFuse 1.7 on OSX 10.5.4,

	ls -ald /Library/Frameworks/MacFUSE.framework
		drwxr-xr-x 6 root admin 204 2008-12-10 19:57 /Library/Frameworks/
MacFUSE.framework/

i've built sshfs (sshfs-fuse-2.1) from src,

	ls -al `which sshfs`
		-rwxr-xr-x 1 root admin 67432 Aug 12 20:58 /usr/local/bin/sshfs

	sshfs --version
		SSHFS version 2.1
		MacFUSE library version: FUSE 2.7.3 / MacFUSE 1.7.1
		MacFUSE mount version 1.7.1
		MacFUSE kernel interface version 7.8

i attempt to mount the remote via sshfs,

	mkdir -p /mnt/fuse_server
	sshfs -F /etc/ssh/ssh_config root <at> server1.loc:/ /mnt/fuse_server -
osshfs_debug,reconnect,volname=FUSE_TEST

but, after locking up terminal for ~ 30 secs, it fails, reporting

	@ server syslog,

		Aug 12 21:09:32 server1.loc sshd[18414]: Accepted publickey for root
from 192.168.1.16 port 1003 ssh2
(Continue reading)

billb | 13 Aug 04:54
Picon

Cannot Find sys/statfs.h


Hi All,

I am trying to build the mythtvfs FUSE for linux on OS X and keep
getting this error on make:

mythtvfs.c:42:24: error: sys/statfs.h: No such file or directory

I was getting the same error for malloc.h but was able to do a find
and specify the full path.  I cannot find statfs.h anywhere though. I
thought that maybe the CFLAGS was not picking up the -D__FreeBSD__=10
variable, but I can see it in the gcc statements on make.

Does anyone have any idea how to get this include working.  I tried
commenting out....it builds but then without statfs it cannot list
directory contents...kinda the whole point.

Thanks
Amit Singh | 13 Aug 04:36
Picon

An Update on Updates


I just released a minor update to the developer release. I encourage
developers to upgrade to it using the autoinstaller.

$ ./autoinstaller -l
# should show 1.9.7 (Leopard) or 1.9.6 (Tiger) being available (at the
time of this writing)

$ sudo ./autoinstaller -i
# should install it

There's a chance some of you might have installed a really early 1.9
developer release that doesn't have the correct version of the
signature computation code that MacFUSE uses. If you have that build,
the autoinstaller will not show an update available (and you can't use
the autoinstaller to upgrade). If you have such a build, please remove
it and explicitly install the new developer build.

This new build includes the following:

* Fixes a code path in the autoinstaller that used HTTP caching when
it shouldn't have been used. This caused the autoinstaller to see
stale information under certain circumstances.

* Gives those who want to bundle the MacFUSE unified package with
their products a way to opt-out of any implicit software updates at
install time. In other words, installation would bypass checking for
updates and only the embedded MacFUSE version will be installed. To do
this, before the autoinstaller runs, you must create (can be an empty
file) /tmp/.macfuse-force-embedded. If you manually call /usr/sbin/
(Continue reading)

Amit Singh | 12 Aug 07:09
Picon

CHANGELOG for Developer Prerelease


The current developer release of MacFUSE has numerous improvements and
new features. Please test those that matter to you and report if
something doesn't work. A preliminary CHANGELOG is reproduced below.

  * Feature: New option `auto_cache`; when you enable this option,
MacFUSE will automatically purge the buffer cache and/or attributes of
files based on changes it detects in modification times. By default,
if MacFUSE detects a change in a file's size during getattr(), it will
purge that file's buffer cache. When auto_cache is enabled,  MacFUSE
will additionally detect modification time changes during getattr()
and open(). Relevant knote messages are also generated. All this is
subject to the attribute timeout. (That is, up to one purge per
attribute timeout window.) As long as your file system's getattr()
returns up-to-date size and modification time information, this should
work as intended. For file systems that wish the kernel to keep up
with "remote" changes, this should obviate the need for explicit
purging through `fuse_purge_np()`.

  * Feature: New user-space library function `fuse_purge_np()`; can be
used by a user-space file system daemon to purge a given file's buffer
cache, tell the kernel that the file's size has changed, invalidate
the file's in-kernel attributes cache, and generate an appropriate
kernel event (kevent) that can be received through `kqueue()`.
[*Experimental*]

  * Feature: New user-space library function `fuse_knote_np()`; can be
used by a user-space file system daemon to generate arbitrary kernel
events (kevent) for a given file. [*Experimental*]

(Continue reading)

kompatibel | 11 Aug 11:45
Picon

after createFile finder sends removeFile


Hello!

I have a problem by creating a file.
I'm Trying to create an own MacFUSE based fileSystem.

if I drop a file into my written filesystem, I get a
"createFileAtPath" request!. But after that request I get a
"removeItemAtPath" request!

Anyone an idea why???

Steffen
Amit Singh | 11 Aug 02:23
Picon

A Note on Boot Camp, Finder Issues


People keep asking about the ntfs-3g and Startup Disk prefpane "issue"
with Boot Camp. If you have ntfs-3g active and have a "Boot Camp"
Windows volume, the latter does not show up in the Startup Disk
prefpane.

The Startup Disk prefpane is simply filtering out (i.e. not
displaying) any mounted volumes that it doesn't consider bootable. Its
definition of a Boot Camp volume includes that the mounted volume
either be of type "msdos" or "ntfs"--this is hardcoded into the
prefpane plugin.

$ cd /System/Library/PreferencePanes/StartupDisk.prefPane/Contents/
MacOS
$ cat StartupDisk | strings | egrep -e 'msdos|ntfs'
msdos
ntfs

That's all there is to it. The volume is still bootable--it's just the
prefpane GUI that's refusing to show the volume. You can hold the opt
key during startup and choose the Windows partition to boot from. You
can also remount it (read-only) using the standard OS X ntfs, and it
should start showing up in the prefpane.

If you think this "breakage" is catastrophic, you should ask Apple to
do something about it.

There are several other cases where OS X is simply not prepared to
deal correctly with non-Apple file systems.

(Continue reading)


Gmane