On Tue, Oct 26, 2010 at 4:41 PM, Dmitry E. Oboukhov <un...@debian.org>wrote:
> Hi, Dmitry! > > I don't reproduce the problem. > > I use mhddfs only from fstab: > > home.uvw.ru:[~]$ grep mhddfs /etc/fstab > > mhddfs#/mnt/first_1T,/mnt/second_1T,/mnt/fourth/common /share/share fuse > user,allow_other,default_permissions,exec 0 0 > mhddfs#/mnt/third/common,/mnt/hda3,/share/hdd1 /share/common fuse > user,allow_other,default_permissions,exec 0 0 > > And it is mounted fine for each booting. So I set unreproducible tag > for this bugreport. > > Pleace, show me a configuration which can't mount mhdd filesystem in > booting. > Configuration: ~$ grep mhddfs /etc/fstab mhddfs#/storage-1Tb,/storage-500Gb /storage fuse allow_other,mlimit=15G 0 2 Insserv version: $ apt-cache policy insserv insserv: Installed: 1.14.0-2 Maybe your configuration does not use insserv? Does your configuration include some hint files for insserv in /etc/init.d? (is "dpkg -L mhddfs | grep etc" empty or not?) If not, could you please verify that your installation lists fuse as prerequisite for any of the moun* scripts like this: $ grep '^mount[^:]*:' /etc/init.d/.depend.boot | grep fuse This was producing empty output for me, until I fixed the bug with quick workaround: $ cat /etc/init.d/mount-mhddfs #! /bin/sh ### BEGIN INIT INFO # Provides: mount-storage # Required-Start: $network fuse # Required-Stop: # Default-Start: S # Default-Stop: # Short-Description: Force mount of mhddfs filesystem on boot ### END INIT INFO mount /storage Notice the "Required-Start: $network fuse". HTH, Dmitry. > > On 11:29 Sun 08 Aug , Dmitry Astapov wrote: > DA> Package: mhddfs > DA> Version: 0.1.37 > DA> Severity: important > > DA> Since recently, "insserv" (a.k.a. dependency-driven boot) is the > DA> preferred way of booting up Debian machines. > > DA> With default insserv setup, fuse is started after the local and remote > DA> filesystems are mounted up, which means that fuse is not available at > DA> the time mhddfs-related entries in /etc/fstab are processed. > > DA> As a result, none of mhddfs filesystems in /etc/fstab are not mounted > at > DA> the end of boot up. > > DA> Bug #555541 seems to contain a recipe for fixing this (it is related > DA> to another fuse-based filsystem, but root cause seems to be the same) > > DA> -- System Information: > DA> Debian Release: squeeze/sid > DA> APT prefers unstable > DA> APT policy: (500, 'unstable'), (500, 'testing') > DA> Architecture: i386 (i686) > > DA> Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) > DA> Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) > DA> Shell: /bin/sh linked to /bin/bash > > DA> Versions of packages mhddfs depends on: > DA> ii fuse-utils 2.8.4-1 Filesystem in USErspace > (utilities > DA> ii libc6 2.11.1-3 Embedded GNU C Library: > Shared lib > DA> ii libfuse2 2.8.4-1 Filesystem in USErspace > library > > DA> mhddfs recommends no packages. > > DA> mhddfs suggests no packages. > > DA> -- no debconf information > -- > ... mpd playing: U.D.O. - They Want War > > . ''`. Dmitry E. Oboukhov > : :’ : email: un...@debian.org jabber://un...@uvw.ru > `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 > `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEAREDAAYFAkzG2msACgkQq4wAz/jiZTdTfQCgzhr8Xp8DQFdcmfT3gprnVfgS > +bIAn0UeMSGrs7gIa7rfXsH1JVWx6G79 > =MdVJ > -----END PGP SIGNATURE----- > > -- Dmitry Astapov
