Skip to contentSkip to conversation

New Debian packages

DISCUSSION Steinar H. Gunderson 3 participants 11 messages Apr 3, 2005 – Apr 13, 2005 Kernel automounter

lore
Share & tools
lore
#0 lore raw

Ian,

I uploaded a couple of new autofs versions to the Debian archive today; you might be interested in some of the patches (mostly minor stuff, like backing down on "set -e" in the init scripts, but there's an odd bugfix in places). Should I send them one by one, or do you just get 4.1.3+4.1.4beta2-7 out of the archive and pick out the patches yourself?

BTW, we're freezing really soon, so if you want something into the Debian version in time for sarge, now is probably the time. :-)

/* Steinar */

Signature · 1 line
Homepage: http://www.sesse.net/
maintainer
#1 lore raw
Quoted 7 lines · Steinar H. Gunderson

Ian,

I uploaded a couple of new autofs versions to the Debian archive today; you might be interested in some of the patches (mostly minor stuff, like backing down on "set -e" in the init scripts, but there's an odd bugfix in places). Should I send them one by one, or do you just get 4.1.3+4.1.4beta2-7 out of the archive and pick out the patches yourself?

I've also been working on this.

I've taken my lead from Debian bug report discussions. I'll check your patches before I put out a new version.

Quoted 3 lines

BTW, we're freezing really soon, so if you want something into the Debian version in time for sarge, now is probably the time. :-)

I'm tempted to release 4.1.4. Most of the current issues are with the Debian portion of the init script which we have been working on.

Do you think we can get this bit right and go straight to release?

Ian

#2 lore raw
Quoted 4 lines · Ian Kent

I'm tempted to release 4.1.4. Most of the current issues are with the Debian portion of the init script which we have been working on.

Do you think we can get this bit right and go straight to release?

The only gripe I can find seems to be the replication, but that is probably too much to fix for 4.1.4. So a release seems OK, yes.

/* Steinar */

Signature · 1 line
Homepage: http://www.sesse.net/
maintainer
#3 lore raw
Quoted 8 lines · Steinar H. Gunderson
Quoted 4 lines · Ian Kent

I'm tempted to release 4.1.4. Most of the current issues are with the Debian portion of the init script which we have been working on.

Do you think we can get this bit right and go straight to release?

The only gripe I can find seems to be the replication, but that is probably too much to fix for 4.1.4. So a release seems OK, yes.

Do you mean the replicated server code. Yes it was broken and still needs more work. However I've tickled it again and it should be at least functional.

Ian

maintainer
#4 lore raw
In reply to Steinar H. Gunderson
Quoted 7 lines · Steinar H. Gunderson

Ian,

I uploaded a couple of new autofs versions to the Debian archive today; you might be interested in some of the patches (mostly minor stuff, like backing down on "set -e" in the init scripts, but there's an odd bugfix in places). Should I send them one by one, or do you just get 4.1.3+4.1.4beta2-7 out of the archive and pick out the patches yourself?

I've checked the patches and here's what I've got:

052 - applied
053 - equivalent change already in place
054 - backout my changes and apply
055 - will apply
056 & 57 - will apply but think scripts are now Boune shell complaint 058 - equivalent change already in place
059 - applied

So this looks good to me.

Quoted 3 lines

BTW, we're freezing really soon, so if you want something into the Debian version in time for sarge, now is probably the time. :-)

Do we have enough time for another beta and some testing time or prehaps it's release time given the above.

I need to test localy after I make these changes anyway so it's going to be a couple of more days.

Ian

#5 lore raw
Quoted 1 line · Ian Kent

053 - equivalent change already in place

Note that there already was an "equivalent" change in beta2, but it was wrong. Have you fixed it properly this time? :-)

Quoted 2 lines

Do we have enough time for another beta and some testing time or prehaps it's release time given the above.

The version number doesn't really matter to me, so call it whatever you'd like; 4.1.4 would probably be fine.

/* Steinar */

Signature · 1 line
Homepage: http://www.sesse.net/
maintainer
#6 lore raw
Quoted 5 lines · Steinar H. Gunderson
Quoted 1 line · Ian Kent

053 - equivalent change already in place

Note that there already was an "equivalent" change in beta2, but it was wrong. Have you fixed it properly this time? :-)

Think so.
That's the nsswitch.conf tab problem.

Ian

#7 lore raw

sgi IRIX-6.5 autofs

I have a situation on IRIX where I am stat'ing a filesystem that is not exported to the IRIX system. The syslog says 'permission denied'. That's expected. Since the directory I'm in has 600 links to the file system that is not exported, autofs keeps trying to mount and keeps getting 'permission denied'.

On linux I get 'permission denied', but it doesn't try to mount again for 30 minutes.

Has anyone heard of such a problem with IRIX's autofs and is there a fix? Why does linux only try every 30 minutes?
TIA.

IRIX system:

Quoted 1 line

uname -aR

IRIX64 r8 6.5 6.5.14f 10100655 IP27

Quoted 1 line

versions -b | grep -i nfs

I nfs 10/28/2002 Network File System, 6.5.14f

LINUX system:

Quoted 1 line

uname -ar

Linux lis9.rhythm.com 2.4.26 #9 SMP Fri May 7 18:22:13 PDT 2004 i686 unknown

Quoted 1 line

/usr/sbin/automount4 -v

Linux automount version 4.1.0

Signature · 7 lines
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rhythm & Hues
5404 Jandy Place
Los Angeles, CA 90066
Voice: 310 448-7763
Fax:   310 448-7600
[email protected]
maintainer
#8 lore raw

Re: sgi IRIX-6.5 autofs

Quoted 11 lines · Greg Bradner

I have a situation on IRIX where I am stat'ing a filesystem that is not exported to the IRIX system. The syslog says 'permission denied'. That's expected. Since the directory I'm in has 600 links to the file system that is not exported, autofs keeps trying to mount and keeps getting 'permission denied'.

On linux I get 'permission denied', but it doesn't try to mount again for 30 minutes.

Has anyone heard of such a problem with IRIX's autofs and is there a fix? Why does linux only try every 30 minutes?

I'm not sure why Linux is trying every thirty minutes. There's not explicit retry login in autofs.

AFAIK it should only try to mount the target of the symlink when an access is attempted.

Ian

#9 lore raw

Re: sgi IRIX-6.5 autofs

Quoted 13 lines · Ian Kent
Quoted 8 lines · Greg Bradner

I have a situation on IRIX where I am stat'ing a filesystem that is not exported to the IRIX system. The syslog says 'permission denied'. That's expected. Since the directory I'm in has 600 links to the file system that is not exported, autofs keeps trying to mount and keeps getting 'permission denied'.

On linux I get 'permission denied', but it doesn't try to mount again for 30 minutes.

Has anyone heard of such a problem with IRIX's autofs and is there a fix? Why does linux only try every 30 minutes?

Quoted 8 lines

I'm not sure why Linux is trying every thirty minutes. There's not explicit retry login in autofs.

AFAIK it should only try to mount the target of the symlink when an access is attempted.

Ian

Let me explain: I have one NAS1 server that has a large number of links to another NAS2. When I run a specific program, an in house tool, it stats the links; which in turn tries to mount NAS2. With the large number of links, the program will stat one, get 'permission denied', and moves to the next. On IRIX, autofs tries to mount with each stat. On linux, it stats the link, but doesn't try to mount each time, rather every 30 minutes. My main curiosity is whether or not Linux autofs caches the status in some way and won't retry for 30 minutes?

Signature · 7 lines
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rhythm & Hues
5404 Jandy Place
Los Angeles, CA 90066
Voice: 310 448-7763
Fax:   310 448-7600
[email protected]
maintainer
#10 lore raw

Re: sgi IRIX-6.5 autofs

Quoted 31 lines · Greg Bradner
Quoted 18 lines · Ian Kent
Quoted 6 lines · Greg Bradner

I have a situation on IRIX where I am stat'ing a filesystem that is not exported to the IRIX system. The syslog says 'permission denied'. That's expected. Since the directory I'm in has 600 links to the file system that is not exported, autofs keeps trying to mount and keeps getting 'permission denied'.

Quoted 7 lines

On linux I get 'permission denied', but it doesn't try to mount again for 30 minutes.

Has anyone heard of such a problem with IRIX's autofs and is there a fix? Why does linux only try every 30 minutes?

Quoted 9 lines

I'm not sure why Linux is trying every thirty minutes. There's not explicit retry login in autofs.

AFAIK it should only try to mount the target of the symlink when an access is attempted.

Ian

Quoted 10 lines

Let me explain: I have one NAS1 server that has a large number of links to another NAS2. When I run a specific program, an in house tool, it stats the links; which in turn tries to mount NAS2. With the large number of links, the program will stat one, get 'permission denied', and moves to the next. On IRIX, autofs tries to mount with each stat. On linux, it stats the link, but doesn't try to mount each time, rather every 30 minutes.
My main curiosity is whether or not Linux autofs caches the status in some way and won't retry for 30 minutes?

Once again I'm unsure of what should be happening.

autofs on Linux shouldn't mount at all on stat unless the target is contained within (not the mount point itself) the filesystem.

In fact it stat should return lies (actually the autofs filesystem node) about the target.

There isn't any retry logic in the code.
AFAIK there would need to be some process scanning the directories for this retry to happen.

I haven't used IRIX autofs for a long time.

Ian