On Mon, 2018-12-03 at 17:38 +, Rick Stevens wrote:
> On 12/1/18 1:49 AM, Patrick O'Callaghan wrote:
> > On Sat, 2018-12-01 at 08:03 +0800, Ed Greshko wrote:
> > > On 12/1/18 6:33 AM, Patrick O'Callaghan wrote:
> > > > I'm getting "filesystem not responding" messages from an NFS-mounted
> > > >
On 12/1/18 1:49 AM, Patrick O'Callaghan wrote:
> On Sat, 2018-12-01 at 08:03 +0800, Ed Greshko wrote:
>> On 12/1/18 6:33 AM, Patrick O'Callaghan wrote:
>>> I'm getting "filesystem not responding" messages from an NFS-mounted
>>> NAS which I suspect is just slow (it spins down its disks when not in
On Tue, 2018-12-04 at 00:20 +1030, Tim via users wrote:
> Allegedly, on or about 30 November 2018, Patrick O'Callaghan sent:
> > When I tried to list a directory on the system it didn't respond, but
> > doing an ssh to the box spins up the disks and lets me log in. So
> > I've no idea what exactly
On 12/3/18 9:50 PM, Tim via users wrote:
> Allegedly, on or about 30 November 2018, Patrick O'Callaghan sent:
>> When I tried to list a directory on the system it didn't respond, but
>> doing an ssh to the box spins up the disks and lets me log in. So
>> I've no idea what exactly automount is suppo
Allegedly, on or about 30 November 2018, Patrick O'Callaghan sent:
> When I tried to list a directory on the system it didn't respond, but
> doing an ssh to the box spins up the disks and lets me log in. So
> I've no idea what exactly automount is supposed to be doing.
I have a similar issue. If
On Sat, 2018-12-01 at 20:15 +0800, Ed Greshko wrote:
> On 12/1/18 7:55 PM, Patrick O'Callaghan wrote:
> > Without the '-f' it simply wouldn't unmount for me (it just sat there),
> > so maybe your setup is different. Either way it's working now so thanks
> > anyway.
>
> Good.
>
> I have had very l
On 12/1/18 7:55 PM, Patrick O'Callaghan wrote:
> Without the '-f' it simply wouldn't unmount for me (it just sat there),
> so maybe your setup is different. Either way it's working now so thanks
> anyway.
Good.
I have had very little, I'd even say no, problems with NFS. Especially after
adding
On Sat, 2018-12-01 at 19:18 +0800, Ed Greshko wrote:
> On 12/1/18 7:14 PM, Patrick O'Callaghan wrote:
> > On Sat, 2018-12-01 at 18:04 +0800, Ed Greshko wrote:
> > > > > I know you have it working
> > > > >
> > > > > But I did verify that unmounting and remounting with a changed
> > > > > para
On 12/1/18 7:14 PM, Patrick O'Callaghan wrote:
> On Sat, 2018-12-01 at 18:04 +0800, Ed Greshko wrote:
I know you have it working
But I did verify that unmounting and remounting with a changed parameter
has no effect.
>>> Except that it did have an effect. I used 'umount -f
On Sat, 2018-12-01 at 18:04 +0800, Ed Greshko wrote:
> > > I know you have it working
> > >
> > > But I did verify that unmounting and remounting with a changed parameter
> > > has no effect.
> > Except that it did have an effect. I used 'umount -f ...' and then
> > 'mount -a' and it worked.
On 12/1/18 5:49 PM, Patrick O'Callaghan wrote:
> On Sat, 2018-12-01 at 08:03 +0800, Ed Greshko wrote:
>> On 12/1/18 6:33 AM, Patrick O'Callaghan wrote:
>>> I'm getting "filesystem not responding" messages from an NFS-mounted
>>> NAS which I suspect is just slow (it spins down its disks when not in
On Sat, 2018-12-01 at 08:03 +0800, Ed Greshko wrote:
> On 12/1/18 6:33 AM, Patrick O'Callaghan wrote:
> > I'm getting "filesystem not responding" messages from an NFS-mounted
> > NAS which I suspect is just slow (it spins down its disks when not in
> > use). I'm using automount and that appears to
On 12/1/18 6:33 AM, Patrick O'Callaghan wrote:
> I'm getting "filesystem not responding" messages from an NFS-mounted
> NAS which I suspect is just slow (it spins down its disks when not in
> use). I'm using automount and that appears to be related as it never
> used to happen with normal mounting.
On Fri, 2018-11-30 at 16:19 -0700, Joe Zeff wrote:
> On 11/30/2018 03:33 PM, Patrick O'Callaghan wrote:
> > How can I get this to work without rebooting?
>
> Have you tried unmounting it and then remounting it? Not sure why it
> would work if mount -a doesn't, but it doesn't take long to make su
On Fri, 2018-11-30 at 22:56 +, Rick Stevens wrote:
> On 11/30/18 2:33 PM, Patrick O'Callaghan wrote:
> > I'm getting "filesystem not responding" messages from an NFS-mounted
> > NAS which I suspect is just slow (it spins down its disks when not in
> > use). I'm using automount and that appears
I have often see cases where servers apparently got mad
at specific systems and started refusing to allow them to mount
(even though there were valid export entries for them).
I have fixed this by restarting nfs on the server side.
___
users mailing list
On 11/30/2018 03:33 PM, Patrick O'Callaghan wrote:
How can I get this to work without rebooting?
Have you tried unmounting it and then remounting it? Not sure why it
would work if mount -a doesn't, but it doesn't take long to make sure.
___
users m
On 11/30/18 2:33 PM, Patrick O'Callaghan wrote:
> I'm getting "filesystem not responding" messages from an NFS-mounted
> NAS which I suspect is just slow (it spins down its disks when not in
> use). I'm using automount and that appears to be related as it never
> used to happen with normal mounting
18 matches
Mail list logo
