The partition wasn't mentioned in the backup report at all (as savefs doesn't 
"see" it, this isn't
surprising.) This should have been a clue that something was wrong but it got 
missed for over a
year. Omissions don't stand out in the backup report in the same was as an 
error would.



I think your right, the server admin entered /usr/local/ at install time and 
the RedHat installer
accepted it. This might be a RedHat bug because the trailing slash is 
superfluous but as RedHat
built with it I think Legato should be able to deal with it.



To experience this bug I believe you need both a trailing / and the partition 
to be specified by
label. I've created some test partitions and it seemed as it you needed both 
components for it to
fail.



As we had made the mistake on our system (and not realised) I thought it was 
worth publicising it
incase anyone else had made the same error.



Paul



----- Original Message -----
From: "Scott Russell" <lnxgeek AT US.IBM DOT COM>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Friday, June 06, 2003 8:17 PM
Subject: Re: [Networker] Linux servers with All specified as the saveset. 
(Serious bug/RFE)


On Fri, Jun 06, 2003 at 05:21:42PM +0100, Paul Brears wrote:
> We've just noticed something rather concerning with a Linux client on our 
> network.
> We had specified 'All' as the saveset and had expected it to backup all the 
> mounted filesystems.
>
> This isn't unfortunately wasn't the behaviour we saw.
>
> One mount point had been specified as /usr/local/ and NetWorker didn't see 
> this filesystem when it
> used savefs to decide what firesystems to backup. (It didn't report any 
> errors, or anything to
> indicate it didn't like this mount point, it just ignored it.)

What about in the backup reports? Did anyone notice the /usr/local partition
missing from the report of this system? Or are you saying Networker included
the /usr/local partition in the save set report but didn't really back it up?

> If you remove the trailing / from the mount point in fstab everything works 
> OK.
> The client was running RedHat 7.0 (with NetWorker 6.1.1) and the filesystem 
> had been created in
this
> way at install time. The other mount points had been created without a 
> trailing /.

I'm guessing that at install time someone entered "/usr/local/" as the
mount point while setting up the partitions. I have several 7.3 and 9.0
installed systems right now, none of them have trailing slashes for the
mount point.

> It would appear that it only affects systems where labels are used in fstab 
> (RedHat 7.0 >) I've
> reproduced this on RedHat 9.0 as well.

I'm confused by what you are saying here. Previously you were talking about
trailing slashes on the mount point. Here you state that the volume label
apparently has something to do with the problem as well?

> We've raised this with our support provider and they are suggesting this is a 
> bug in Linux because
> Linux strips the trailing / from the mount point in mtab and because these 
> are different,
NetWorker
> doesn't backup the filesystem.

I'm uncertain how Networker determines what is and is not a partition but
would tend to agree that either fstab or mtab or both are involved. I would
personally consider a trailing slash on the mount point in fstab a typo,
it isn't needed and shouldn't be there.


--
Scott Russell <lnxgeek AT us.ibm DOT com>
IBM Linux Technology Center, System Admin

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=