1753510 Members
5243 Online
108795 Solutions
New Discussion юеВ

Re: Urgent

 
SOLVED
Go to solution
S.S.
Super Advisor

Re: Urgent

Hi Kapil,

Please see the attached file.

During Creation of new filesystems i have used the following command.
For example:

# newfs -F vxfs -o largefiles /dev/test4db2/rtest4db2


Thanks & Regards
Kapil Jha
Honored Contributor

Re: Urgent

If your file system is mounting manually fine.
Then there is no error in creating them,
issue is with automatically mounting it while system reboots so fstab file is the file which is responsible for that.

I suspect there is some white character in this file while u added the new FS.
So i would suggest to remove entries of this file system from fstab and re-enter them carefully.

to check you may have to umount the already mounted FS.

BR,
Kapil+
I am in this small bowl, I wane see the real world......
S.S.
Super Advisor

Re: Urgent

Hi Kapil,

Thank you.

Because of you i was carefully read the lines in /etc/fstab and found i mis-typed the word datainlog as detainlog.

Thanks for your great help! :-)



S.S.
Super Advisor

Re: Urgent

Thank you!
Kapil Jha
Honored Contributor

Re: Urgent

haha....I also checked if something misspelling but I could not see that :)
you have a good eye

BR,
Kapil+
I am in this small bowl, I wane see the real world......
Steve Post
Trusted Contributor

Re: Urgent

um......
correct me if I am wrong.....

I thought that when you use MC serviceguard you never put the filesystem into the fstab file if it is part of a package. That there is a process within MC serviceguard that performs the mounting of the file system that are part of the package.

If ServiceGuard was a person it would be saying "HEY! Who the heck already mounted this stuff? That's my job. Those filesystems are supposed to be on the alternate node right now."