Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

Remove a file domain after a domain panic without reboot?

Adam Garsha
Valued Contributor

Remove a file domain after a domain panic without reboot?

It is possible to remove a file domain that has panic'd due to a device failure? (so that I can recreate it with a new device).

I've tried:

prompt> fuser -ck /bad/filesystem
prompt> umount /bad/filesystem
/bad/filesystem: "Device busy"

prompt> rmfdmn bad_domain
rmfdmn: Fileset bad_domain mounted on /bad/filesystem in domain bad_domain.
All bitfile sets must be dismounted prior to removal.
rmfdmn: can't remove domain 'bad_domain'
10 REPLIES
Victor Semaska_3
Esteemed Contributor

Re: Remove a file domain after a domain panic without reboot?

Sounds like Tru64 still sees it as mounted. I suggest 1st trying the umount command with the -f option.

Vic
There are 10 kinds of people, one that understands binary and one that doesn't.

Re: Remove a file domain after a domain panic without reboot?

try voledit -rm domain_name
Venkatesh BL
Honored Contributor

Re: Remove a file domain after a domain panic without reboot?

Is any fileset of the domain still mounted? Check the output of 'mount' command. You can use the 'fuser' command to see if any process is still referring to the file system.

Also, voledit is an LSM command. I don't think its related to AdvFS domain.
Ivan Ferreira
Honored Contributor

Re: Remove a file domain after a domain panic without reboot?

From the mount man page:

-f Performs a fake mount and actually does not mount the file system. This option is used to verify the arguments you plan to use with the mount command.

I think that this wont force the umount, but you can try. If this is a cluster file system, you can try using:

cfsmgr -u

And ensure that no other members are using the file system.

Your last option is to reboot.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Victor Semaska_3
Esteemed Contributor

Re: Remove a file domain after a domain panic without reboot?

Ivan,

You're looking at the -f option for mount. Further down in the manpage it says for umount:

-f Performs a fast unmount operation that causes remote file systems to be unmounted without notifying the server.

I've used it for such problems and usually works.

Vic
There are 10 kinds of people, one that understands binary and one that doesn't.
Ivan Ferreira
Honored Contributor

Re: Remove a file domain after a domain panic without reboot?

You are right Victor. Thanks for the clarification. I did not read all the man page.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Adam Garsha
Valued Contributor

Re: Remove a file domain after a domain panic without reboot?

cfsmgr -u worked on one of our clusters but the other one is too wacked-out. Anything AdvFS related e.g. showfdmn, showfsets,... etc. hangs on one of the clusters and a reboot is the only option.
Venkatesh BL
Honored Contributor

Re: Remove a file domain after a domain panic without reboot?

1) You could try 'fuser' to see if any process is still using the files.

2) If you have the 'dbx' tool, you could do "dbx -k /vmunix" and check out what the AdvFS commands are waiting on.

3) If you have 'truss' tool, you could initiate the AdvFS command with truss ("truss "). This would tell you where the command is stuck!
Michael Schulte zur Sur
Honored Contributor

Re: Remove a file domain after a domain panic without reboot?

BL,

after fuser -ck /bad/filesystem there shouldn't be anyone.

greetings,

Michael
Aco Blazeski
Regular Advisor

Re: Remove a file domain after a domain panic without reboot?

Hi all,

I had such experience also, where "fuser -ck" and "umount -f" don't do the job.
This usually was the case when there are open inodes on some file, but file is deleted.
The solution would be to identify those PIDs which have open inodes and kill them.

On Solaris OS there are some quite usefull tools/commands, but can't find for Tru64 (maybe lsof could do, but never tried).

So on Tru64 this kind of problem I usually solve with reboot :-|.