Automatic creation of home directoires and reporting the back the size of the hard quota threshold.

[SCR512]

Is anyone utilizing the automatic home directory provisioning stuffs in OneFS? 

In our environment we are using this but ran into a snafu with linked user quotas not giving us the ability to report back the size of the linked quota to the end user. So the enduser might have a 5GB quota but they see the entire cluster size if they map that SMB share. Makes for fun/confusing times.

I ran across an article that seems to remedy this? (I've not tested this on our DR cluster yet) http://vcevblog.com/?p=94

[Kevin McDonald]

We're using it and have seen the same display behavior - which is confusing to end users.  (We are 6.5.5.11 right now.)  We use a 5G default quota, but they see a 1TB limit from the clients.     We are going to try this fix out to see if it makes it any better.  Looks like you can only specify one value though?  We have some users with custom quotas ...

KMac 

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
-Kevin.

[Paul Williams]

The issue here is that you cannot apply the container option to a user (or for that matter group) quota.  It is this container option that reports to the client the total space available and it is only available on directory quotas.

[Peter Serocka]

The key is to not use linked user quotas
but directory quotas (one per each user's home)
and set the container flag.

Which is exactly what the script presented
in http://vcevblog.com/?p=94 does.

Using that script, different quotas for somes users can
be set under ”root preexec”,
when you replace the static "isi quota ..." command
by a script that pulls the intended quota value
from some config or rule set, and then runs isi quota.

Peter

[Paul Williams]

This correct. A great solution would be for Isilon to provide an inherited directory quota functionality, so that for each new directory that gets created it automatically inherits a directory quota of x size that has the container option set. This would save the need for manually creating the quota, or have a script run through the directory tree looking for directories that do not have a quota applied.

Cheers,

Paul

[Kevin McDonald]

Ok - I see.  Yes, an inherited directory quota sure would be nice - thanks!

[SCR512]

So... trying this on my DR cluster which is running OneFS 7.0.1.2 I'm not having luck getting this to work. This is after I fixed up the isi quota command as it's different in 7.x. Anyone have this sorta template working in 7.x? :)

[Aglidic]

Hi guys,

do you find a solution for this on  onfeFS 7?

I try the script from the blog, i modified it to the command of oneFS 7 but still nothing.
Thanks

[Peter Serocka]

Does the script actually get executed?

What do you see when you capture standard output and error to a file?
like

value=" ... > /tmp/homescript.out 2> /tmp/homescript.err"

(ampersand-gt-; will become > , 2ampersand-gt-; will become 2> )


Peter

[Aglidic]

hum didn't check that, did you success to make it work on oneFS 7?

[Peter Serocka]

On Tue 30 Apr '13 md, at 09:38 st, Aglidic wrote:

> hum didn't check that, did you success to make it work on oneFS 7?

I don't have OneFS 7 at my hand now, but that issue should be quite
straightforward to sort out by investigation on script level. You
might also pack the mkdir and isi commands into a single script file
like /opt/homescript.sh. That makes it easier to test the actual
scripts manually and to capture logs. And one can write &'s and >'s as
plain &'s and >'s.

Peter