Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

bdf & df -k don't match

Status
Not open for further replies.

Denda

MIS
Oct 30, 2001
237
US
OK - here's a dilly...
We have 2 rp2470's in a cabinet, each with 2 18 G drives & 12 - external 72G hard drives. When I first set these systems up, I had a portion of the hard drives allocated to 1 rp2470 cpu & then had the remaining hard drives allocated to the other rp2470. Everything was great & then I went on vacation... What I'm being told is the secondary rp2470 was all of sudden thinking it was the primary rp2470. No one knows why, it just started happening.. yeah, right.. My replacement reset the hostname & ip address to the correct hostname & ip address after he was notified aprox 4 days after this must have started happening. Everyone thought it was fixed & never bothered letting me know, until now.. 1 1/2 month later. It looks as though someone copied over the /etc directory FROM the primary server to the secondary server. Everything on the secondary server is now an exact duplicate of the primary. I can run a bdf & the results are exactly the same as the primary server, if I do a df -k the results are the original layout. Can I just comment out the incorrect mnttab file entries from the primary server & re-allocate the correct physical disks to the secondary server? These are new servers & aren't in production yet, but a ton of work has been done on the primary server, with the secondary just starting to be worked on now, hence the problem was discovered. By the way, no one & I mean no one now has root pwd on these systems, but myself!
 
> Can I just comment out the incorrect mnttab file entries from the primary server & re-allocate the correct physical disks to the secondary server?

Make a backup of your current /etc/mnttab and create a new one with setmnt (or edit it by hand if you're comfortable with that - the man page on my HPUX box calls this a Bad Thing).

> By the way, no one & I mean no one now has root pwd on these systems, but myself!

Any idea how /etc could be blown away without root access? It might not be a bad idea to change the root password and enable shadow passwords (if not already enabled).

> No one knows why, it just started happening.. yeah, right.

Public summary executions will solve this :)
 
Thanks for the advice Jason.
I did as you advised & that worked until I rebooted & then everything was back as it was before with being an exact duplicate on the primary server. Anything else I have to do to make this stick? Thanks again
 
Are one of the startup scripts overwriting /etc/mnttab? It might be worthwhile to grep the scripts for mnttab or setmnt.

Let us know how what that turns up.
 
I think you need to make permanent changes to the /etc/fstab file, those will roll over to the mnttab file..

Bob
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top