Ticket #461 (closed defect: fixed)

Opened 15 years ago

Last modified 14 years ago

pyhesiodfs should pass -o nonempty to fuse

Reported by: andersk Owned by:
Priority: normal Milestone:
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:


pyhesiodfs fails to start up on a nonempty /mit.

root@ringworld:/etc/init.d# /usr/bin/pyhesiodfs /mnt
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
Traceback (most recent call last):
  File "/usr/bin/pyhesiodfs", line 226, in <module>
  File "/usr/bin/pyhesiodfs", line 223, in main
  File "/usr/lib/python2.6/dist-packages/fuse.py", line 713, in main
fuse.FuseError: filesystem initialization failed

From fuse/README:


  Allows mounts over a non-empty file or directory.  By default these
  mounts are rejected (from version 2.3.1) to prevent accidental
  covering up of data, which could for example prevent automatic

Change History

comment:1 Changed 15 years ago by broder

  • Status changed from new to proposed

comment:2 Changed 14 years ago by broder

  • Status changed from proposed to closed
  • Resolution set to fixed

Moved to production a while back.

Note: See TracTickets for help on using tickets.