public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: ionut cucu <cuciferus@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] [OT]nfs question
Date: Tue, 18 Mar 2008 18:37:52 +0200	[thread overview]
Message-ID: <20080318183752.63997fd6@cuci> (raw)

Hi list!
I want to share my files in my lan with various files systems. I've
tried so far sshfs and now nfs but both have the following issue:
should the router/hub go down, or one of participants to my
inner-circle sharing buddies close their pc, neither of the rest can
enter home...we all have the nfs/sshfs mounted
in /home/user/otheruserdir. I tried restarting nfs/nfsmount nothing.
Umounting will not work because "umount.nfs: Server failed to unmount
'10.6.3.41:/home/cuci' umount2: Device or resource busy
umount.nfs: /home/iosz/temp: device is busy" --as an example. And lsof
gets stuck. Any ideas on how to avoid this?
-- 
gentoo-user@lists.gentoo.org mailing list



             reply	other threads:[~2008-03-18 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 16:37 ionut cucu [this message]
2008-03-18 17:00 ` [gentoo-user] [OT]nfs question Florian Philipp
2008-03-18 17:23 ` Neil Bothwick
2008-03-18 18:38   ` Strong Cypher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080318183752.63997fd6@cuci \
    --to=cuciferus@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox