Sim link or a better option
 

Hello,

I have a file server that was built before my time here. Unfortunately it was not built very well, and of course it became more and more important to production.

Using LVM the following was created:
/dev/mapper/vg_weather-sff_share 34T 30T 3.4T 90% /sff_share

This is currently made up of 30 + different volumes. I do not want to continue growth here. Our developers need to be able to write to the date in /sff_share. The data is to large to be moved or copied.

I was thinking about creating a new fresh mount /sff_share1 and building a sim link to /sff_share so that the data will still be able to be accessed, but new data will be written to he fresh file system / volume attached to /sff_share1. So to the script everything can be accessed under /sff_share.

Does this sound like a good route? Or might there be a better option.

1. I need to get write to stop on the current /sff_share
2. New data needs to write to /sff_share1
3. Both /sff_share and /sff_share1 need to be accessible under /sff_share

Sim link or a better option
 

you can use --bind option of mount command to connect sff_share1 to some where in sff_share or you can mount sff_share1s disk in side sff_share

If I bind, I think I will be writing to both