mount point vs management

[christian_derek]

Hi,

I’m running hpux 11iv3 with an eva in backend. The system is share between client and each client have few env (prod, preprod,test)

• I presented to the hpux a lun per client env (client1_prod, client1_test,etc)
• I have built a vg per client env (vg_client1_prod, vg_client1_test)
• Built multiple lv per vg (/dev/vg_client1_prod/lvol_data,/dev/vg_client1_prod/lvol_opt,etc)

My questions is, how should I deploy it at the file system.

Ideally, I would like to have something similar to this …
/prod/client1/data
/prod/client1/opt
…
/prod/client10
/test/client1/data…

Should I :

Create symlink
- Vg00 will contain /opt/company/client1/prod
- Create symlink from the previous path to /prod/client1/data on the vg_client1_prod
- Pros and cons?


Mount in the right directory
- Create my file system from /dev/vg_client1_prod/lvol_data to /opt/company/client1/data
- Pros and cons

Or better solution?

Thanks,

[James R. Ferguson]

Hi:

Instead of six (6) separate threads that deal with the same fundamental question, you would be better served either (1) referencing the URL's of the latest thread with its predecessor; or (2) not starting a new thread at all, but continuing to refine the discussion in one thread until you are satisfied.

Of course, providing feedback (yes, points do equate to that) as you proceed is also, always appreciated. Points also help responders guage how they might have helped and where additional responses may add further value.

...JRF...

[SoorajCleris · Accepted solution]

Hi Christian,

Just create the directories like /prod/client1/data


Use newfs command to create filesystem

#newfs -F vxfs /dev/vg_client1_prod/rlvol_data

Then use mount comamnd to mount.

mount /dev/vg_client1_prod/lvol_data /prod/client1/data

Put the entries in /etc/fstab

Regards,
Sooraj

[christian_derek]

Hi Sooraj,

My point is if I mount, let say 5 fs like this with newfs + mount command:

/prod/client1/data
/prod/client1/opt
/prod/client1/etc/
/prod/client1/var
/prod/client1/other

if by mistake, one of my programmer is building a file in /prod/client1 and not the right mount point. In which lv the file will reside, the first mount point?

thanks,

[Dennis Handly]

>In which lv the file will reside, the first mount point?

On your root disk, or whatever filesystem contains /prod/client1/.

[christian_derek]

so,

what you are saying is that I will need to build my structure on vg00 /prod/client1, is this ok? This is the right way to do?

Thanks,

[Dennis Handly]

>what you are saying is that I will need to build my structure on vg00 /prod/client1, is this ok?

The only thing I implied was not to make the mistake of putting anything in /prod/client1/, only in your 5 subdirectories.

To prevent mistakes, you can remove write access to /prod/client1/.

[Dennis Handly]

>I will need to build my structure on vg00 /prod/client1?

If you were asking do you need to do the following before you mount, yes:
mkdir -p /prod/client1/data /prod/client1/opt /prod/client1/etc/ \
/prod/client1/var /prod/client1/other

[christian_derek]

I have 2 other questions ...

1- why the options -p if the mkdir

2- so my vg mount point need to be on top of the dir structure of my vg00?

Thansk,

[Mel Burslan]

>> 1- why the options -p if the mkdir

-p option is there to create any intermediary subdirectories that may not exist on your loooong path.

For instance

lets assume you do not have anything under /prod. In order to create /prod/client1/data, you will need to do

mkdir /prod/client1
mkdir /prod/client1/data

-p option eliminates the need to use two mkdir statements and create the /prod/client1 on the fly for you when you execute

mkdir -p /prod/client1/data

command.

>> 2- so my vg mount point need to be on top of the dir structure of my vg00?

well, yes. Considering "/", i.e. the root of all filesystems is actually a filesystem residing on vg00, all filesystems created are actually dangling off of the vg00. So there is no escaping from it.

[christian_derek]

hopefully my last questions,

since I will need to build on vg00:

/prod/client1/data
...
/test/client/data

should my /prod, /test and /preprod been logical volume ?

thanks,

[Mel Burslan]

It is a matter of preference in my opinion, if it needs to be a simple directory or a filesystem, if there is not much to be stored in there, maybe a init script or two. It is best to make the highest point in the directory tree where the application or its lueless users, store large datafiles, a separate logical volume and filesystem, then mount it, so that their action will not cause grief as far as operating system disk go.

Consider, application using this area as a scratch-pad, by creating hundreds, if not thousands of temporary files every minute. If this happens on the disk where vg00 is located, it may impact your OS and make it slower. Take this as an example why you should separate them physically.

[christian_derek]

final question

what should we do regarding file path localisation?

should we build a symlink from

/opt/company1/prod/bin to /prod/client1/opt/bin?

or change application path location to point directly at /prod/client1/opt

Thanks,

[Mel Burslan]

Creating symbolic links is an alternate way to provide accessibility but if you have a chance to define the paths in the application itself, I'd go with that as a preference. I know some applications are not happy about dealing with symlinks. Without knowing the nature of your application, mine is just a preference statement. You can go either, or ...

[christian_derek]

thank you all