My understanding was that this was perfectly acceptable in a GPFS system. i.e.
mounting parts of file-systems in others. It has been suggested to us as a way
of using different vendor GPFS systems (e.g. an ESS with someone elses) as a
way of working round the licensing rules about ESS and
Just the risk your parent system dies which will block your access to the
child file system mounted on a mount point within.
If that is not bothering , go ahead mount stacks . As for the symling
though : it is also gone if the parent dies :-).
Mit freundlichen Grüßen / Kind regards
Dr. Uwe
> On Nov 19, 2020, at 10:49 AM, Jonathan Buzzard
> wrote:
>
> On 19/11/2020 15:34, Caubet Serrabou Marc (PSI) wrote:
>> Hi,
>> I have a filesystem holding many projects (i.e., mounted under /projects),
>> each project is managed with filesets.
>> I have a new big project which should be placed
On 19/11/2020 18:13, Caubet Serrabou Marc (PSI) wrote:
Hi all,
thanks a lot for your comments. Agreed, I better avoid it for now. I was
concerned about how GPFS would behave in such case. For production I
will take the safe route, but, just out of curiosity, I'll give it a try
on a couple
Hi all,
thanks a lot for your comments. Agreed, I better avoid it for now. I was
concerned about how GPFS would behave in such case. For production I will take
the safe route, but, just out of curiosity, I'll give it a try on a couple of
test filesystems.
Thanks a lot for your help, it was
On 19/11/2020 16:40, KG wrote:
You can also set mount priority on filesystems so that gpfs can try to
mount them in order...parent first
One of the things that systemd brings to the table
https://github.com/systemd/systemd/commit/3519d230c8bafe834b2dac26ace49fcfba139823
JAB.
--
Jonathan
On 19/11/2020 17:34, Jan-Frode Myklebust wrote:
I would not mount a GPFS filesystem within a GPFS filesystem.
Technically it should work, but I’d expect it to cause surprises if ever
the lower filesystem experienced problems. Alone, a filesystem might
recover automatically by remounting. But
Agreed, not sure how the GPFS tools would react. An alternative to symlinks
would be bind mounts, if for some reason a tool doesn't behave properly
with a symlink in the path.
On Thu, Nov 19, 2020 at 06:34:05PM +0100, Jan-Frode Myklebust wrote:
> I would not mount a GPFS filesystem within a GPFS
I would not mount a GPFS filesystem within a GPFS filesystem. Technically
it should work, but I’d expect it to cause surprises if ever the lower
filesystem experienced problems. Alone, a filesystem might recover
automatically by remounting. But if there’s another filesystem mounted
within, I
Hi Simon,
that's a very good point, thanks a lot :) I have it remotely mounted on a
client cluster, so I will consider priorities when mounting the filesystems
with remote cluster mount. That's very useful.
Also, as far as I saw, same approach can be also applied to local mounts (via
mmchfs)
Hi Jonathan,
thanks for sharing your opinions. In the sentence "Technically, mounting a
filesystem on top of an existing filesystem should be possible" , I guess I was
referring to that...
I was concerned about other technical reasons, such like how would this would
affect GPFS policies, or
If it is a remote cluster mount from your clients (hopefully!), you might want
to look at priority to order mounting of the file-systems. I don’t know what
would happen if the overmounted file-system went away, you would likely want to
test.
Simon
From: on behalf of
"marc.cau...@psi.ch"
You can also set mount priority on filesystems so that gpfs can try to
mount them in order...parent first
On Thu, Nov 19, 2020, 21:19 Jonathan Buzzard
wrote:
> On 19/11/2020 15:34, Caubet Serrabou Marc (PSI) wrote:
> > Hi,
> >
> >
> > I have a filesystem holding many projects (i.e., mounted
On 19/11/2020 15:34, Caubet Serrabou Marc (PSI) wrote:
Hi,
I have a filesystem holding many projects (i.e., mounted under
/projects), each project is managed with filesets.
I have a new big project which should be placed on a separate filesystem
(blocksize, replication policy, etc. will be
Hi,
I have a filesystem holding many projects (i.e., mounted under /projects), each
project is managed with filesets.
I have a new big project which should be placed on a separate filesystem
(blocksize, replication policy, etc. will be different, and subprojects of it
will be managed with
15 matches
Mail list logo
