Recently active topics in Wuala tagged with nfs

1-10 of 10 topics
  • 8 Replies 3 Followers

    Wuala, Filesystem Integration, and Ubuntu Last reply on June 27, 2008 03:23.

    I am attempting to use the filesystem integration provided by Wuala in Ubuntu, but am running into an issue. I've got the nfs share mounted, everything shows up ok, but if I'm wanting to add files to a playlist in my media player or run unison, it gets choked up with the many gigs worth of data I'm throwing at it. When I add just 13 songs to any media player, it only pulls in a couple then stops. It isn't able to pull all the songs.

    I used the wuala guide on setting up the nfs share in my fstab. Here's the link I followed. http://wua.la/en/kb/4 I noticed the bottom mentioning Ubuntu and have wondered if that is part of my issue.

    Thanks for your help!
    shanepardue shanepardue asked this question on May 08, 2008 15:43. Muffin joined shanepardue and 1 other person asking this question. It's tagged ubuntu, and nfs
  • 0 Replies 1 Follower

    NFS upload from linux client: cannot create file

    linux client: built-in NFS server fails with "cannot create file: unknown error 526" when copying a file with 2097197226 bytes to ~/wuala/...

    Client version: v119, quota 3GB, fstab entry:
    localhost:/wuala /home/[username]/wuala/direct nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183

    Double-clicking at the exact same file on the windows (GUI) client I get "The file has not been completely uploaded. Please try again later or contact its owner".

    So it's maybe just an issue with user interaction / timeout: the file is requested to be uploaded but that just takes a while, and the OS tries to tell the user that it hasn't arrived yet. Is that the correct interpretation? Could that be fixed / clarified? I took the fstab entry from your FAQ, so don't blame me for the timeout value :-)
    k k reported this problem on June 17, 2008 15:38. It's tagged linux, nfs, create, and error
  • 1 Reply 2 Followers

    Failure: rdiff-backup Last reply on June 16, 2008 11:06.

    At first glance, Wuala seems to work okay with 'rsync'.

    However, I can't get it working with "rdiff-backup". I keep getting the "Stale NFS file handle" error. Are you aware of this problem and when will it be fixed?
    Chris Giles Chris Giles reported this problem on June 13, 2008 11:56. It's tagged rsync, and failure
  • 5 Replies 4 Followers

    Wuala direct access seen as full disk by openSUSE 10.3 x86-64 Last reply on June 15, 2008 20:19.

    Software Management under openSUSE's YaST pops up a warning that says "Warning: disk space is running out!" It says I have used 4.0 TB of 4.0 TB in /home/bmccann/wuala/direct. It also lists that path as being full when I am in the actual software management screen.
    chengas123 chengas123 reported this problem on April 23, 2008 20:22. Volker also has the problem chengas123 reported. It's tagged wuala
  • 1 Reply 1 Follower

    files in groups can be deleted without permission Last reply on May 29, 2008 09:32.

    Hi,
    I am running wuala at linux with NFS filesystem integration. When I use "rm file" at a groups folder at the NFS mount, the file gets removed from the group thogh I am missing the rights in that group.

    PS: This "We've estimated the likelihood of your problem getting noticed", "Get emotional! Describe how this topic makes you feel." thing is just silly :P
    eth0 eth0 reported this problem on May 26, 2008 23:15. It's tagged nfs, and permission
  • 0 Replies 0 Followers

    java.io.FileNotFoundException trying to download file

    I'm using wualacmd under CentOS and I'm having problems accessing a file on this host (it seems to work fine from others).

    When I try to cat the file from the NFS mount I get error "Input/output error" and in the client a few seconds later it gives "Wuala>Problem: java.io.FileNotFoundException: /home/wuala_mnt/wuala/wuala/Data/Local2/Large/979CAC0490BD16645B30A41ADA4671554AF0FF6C"

    The file causing this is http://wua.la/Linux+Updates/CentOS/5/... (which is in my public group).

    Chris.
    Chris Burton Chris Burton reported this problem on May 26, 2008 12:46. It's tagged linux, and nfs
  • 15 Replies 3 Followers

    Wuala on openSUSE 10.3 with NFS support Last reply on May 25, 2008 13:50.

    Hi,

    I am running openSUSE 10.3 and want to add the NFS support to my Wuala install. The instructions say to run "apt-get install nfs-common", which sounds like what you should do if you're running Ubuntu. However, on openSUSE I don't see any package called nfs-common. I already have the following installed by default:
    nfs-client
    mfsidmap
    yast2-nfs-client

    There are also a few more available, which I do not have installed:
    nfs-kernel-server
    nfs-server
    yast2-nfs-server

    Do you know if any of these are an equivalent to nfs-common or if any of the additional YaST package repositories like Packman has the package available?
    chengas123 chengas123 asked this question on March 18, 2008 20:44. It's tagged opensuse, and linux
  • 6 Replies 5 Followers

    nfs-Volume unter OSX ist buggy bei Umlauten Last reply on May 22, 2008 15:34.

    Unter osx (10.5 aktuell) sind Dateien im nfs-mount die Umlaute oder Sonderzeichen enthalten tote links. Man kann auf die nicht direkt üas nfs-volume zugreifen.

    .. Die Dateien werden mit ihrem Namen bis zum Umlaut angezeigt und "verschwinden" bei einem Klick drauf.

    Und debian werden die Umlaute oder Sonderzeichen zwar als Fragezeichen angezeigt, aber man kann trotzdem zugreifen.

    Ich bin mir jetzt nicht sicher, ob das ein osx-Problem ist mit allen nfs-volumes ist. Ich hatte nur den Eindruck, dass es ein paar Versionen früoch nicht so war. Da kann ich mich aber komplett irren. :D
    bagelcat bagelcat reported this problem on March 31, 2008 10:41. freedumb2000 also has the problem bagelcat reported. It's tagged osx, and nfs
  • 1 Reply 3 Followers

    filesystem integration not working (nfs error: success !?) Last reply on May 02, 2008 16:14.

    i tried to use filesystem integration on linux (gentoo) but encountered a very strange error named "success".

    #: mount /mnt/wua.la/wuala/direct
    mount: mount to NFS server 'localhost' failed: RPC Error: Success.

    on that computer a nfs-server is running, so i started wuala using the -noportmapregistration option. btw: can this option be entered somehow into wualarc?

    my fstab entry looks like this:
    localhost:/wuala /mnt/wua.la/wuala/direct nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183

    the check reports portmap and service as ok and volume and integration as failed.

    thanks in advance for any hint!
    andy
    superwutze superwutze asked this question on May 01, 2008 18:51. intgr joined superwutze and 1 other person asking this question. It's tagged filesystem integration
  • 0 Replies 1 Follower

    inode-errors bei nfs-server abfragen

    Wollt nur mal saachen, mein syslog meldet bei Listingabfragen relativ oft:

    Apr 10 09:29:37 localhost kernel: nfs_update_inode: inode number mismatch
    Apr 10 09:29:37 localhost kernel: expected (0:12/0x3cc6193d), got (0:12/0x104b007b)

    Der Fehler scheint aber keine weiteren Probleme zu verursachen. Mir sind zumindest keine aufgefallen. Eine kleine googelei ließmich üolgende Aussage stolpern:
    ++snipp1
    Now I think I can see where the problem originates from: nfs-server
    does vfs_getattr() from encode_fattr3(), but it doesn't check the
    return value. So if getattr() fails, the attributes (including the
    inode numebr) will be bogus.

    I'll ask the NFS maintainer about this.
    ++snapp
    ++snipp2
    I think there may be a second, similar bug. Over NFS, a typical
    sequence on the client is:

    OPEN
    WRITE
    CLOSE

    On the server, this looks like:

    OPEN
    WRITE
    FSYNC
    RELEASE

    The kernel nfsd doesn't use FLUSH, and the FSYNC is used to make the
    write stable. However, there seems to be a bug in the nfsd where if
    the WRITE succeeds, but the FSYNC fails, the client is incorrectly
    told the stable write succeeded. For example, see the call to fsync()
    in nfsd_dosync() which is called via nfsd_sync() in nfsd_write(). The
    return code of fsync() isn't checked.
    ++snapp

    Weis nicht ob das Problem wirklich wichtig ist oder ob die Problemlögsansäe helfen. Die Geschichten sind nicht meine Baustelle. :D

    Ich wollte es nur mal mitteilen..

    Die fehlermeldungen sehe ich sowohl unter darwin 10.5.2 als auch unter debian sarge aktuell
    bagelcat bagelcat reported this problem on April 10, 2008 07:53. It's tagged nfs, and inode