Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
1507 views

quota not being applied

Hi guys

I recently did a backfill on an entire container to ensure all users
had a home dir.

I have a quota of 40mb applied to that container's policy.

I also have a few groups in the container that have another policy
associated so I can up the quota on the users in those groups. One of
those is a "Quota Unlimited" group, which has an initial quota of 0.

The backfill on the container naturally reset all users to 40mb.

So, I went to do another backfill on those groups so the higher quota
would be reapplied but it's not working.

The results screen, for each member of the group, says
"No action because of current 40 meg quota. Policy is 40 meg"

HELP!
I've amended the policy to have a 5000 mb quota instead of unlimited,
and done another backfill, same result.

I just tried the same thing on another group and getting the same thing.

Also, the policy has quota manager enabled with no maximum set.. so as
a workaround, I went into quota manager for one of the users but it's
saying there is a 200 mb limit, so i can't increase the quota that way.

So, I currently have users who can't save to their home directories
because the quota isn't being applied.

What's going wrong here?

Thanks,
Dave

--

0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

Dave,
Which backfill are you doing? Are you using the quota backfill?

thanks,
NSM Development

Dave wrote:
> Hi guys
>
> I recently did a backfill on an entire container to ensure all users
> had a home dir.
>
> I have a quota of 40mb applied to that container's policy.
>
> I also have a few groups in the container that have another policy
> associated so I can up the quota on the users in those groups. One of
> those is a "Quota Unlimited" group, which has an initial quota of 0.
>
> The backfill on the container naturally reset all users to 40mb.
>
> So, I went to do another backfill on those groups so the higher quota
> would be reapplied but it's not working.
>
> The results screen, for each member of the group, says
> "No action because of current 40 meg quota. Policy is 40 meg"
>
> HELP!
> I've amended the policy to have a 5000 mb quota instead of unlimited,
> and done another backfill, same result.
>
> I just tried the same thing on another group and getting the same thing.
>
> Also, the policy has quota manager enabled with no maximum set.. so as
> a workaround, I went into quota manager for one of the users but it's
> saying there is a 200 mb limit, so i can't increase the quota that way.
>
> So, I currently have users who can't save to their home directories
> because the quota isn't being applied.
>
> What's going wrong here?
>
> Thanks,
> Dave
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

On Feb 22, 6:29 am, NSM Development <storagemana...@novell.com> wrote:
> Dave,
> Which backfill are you doing? Are you using the quota backfill?
>
> thanks,
> NSM Development
>
>
>
> Dave wrote:
> > Hi guys

>
> > I recently did a backfill on an entire container to ensure all users
> > had a home dir.

>
> > I have a quota of 40mb applied to that container's policy.

>
> > I also have a few groups in the container that have another policy
> > associated so I can up the quota on the users in those groups. One of
> > those is a "Quota Unlimited" group, which has an initial quota of 0.

>
> > The backfill on the container naturally reset all users to 40mb.

>
> > So, I went to do another backfill on those groups so the higher quota
> > would be reapplied but it's not working.

>
> > The results screen, for each member of the group, says
> > "No action because of current 40 meg quota. Policy is 40 meg"

>
> > HELP!
> > I've amended the policy to have a 5000 mb quota instead of unlimited,
> > and done another backfill, same result.

>
> > I just tried the same thing on another group and getting the same thing.

>
> > Also, the policy has quota manager enabled with no maximum set.. so as
> > a workaround, I went into quota manager for one of the users but it's
> > saying there is a 200 mb limit, so i can't increase the quota that way.

>
> > So, I currently have users who can't save to their home directories
> > because the quota isn't being applied.

>
> > What's going wrong here?

>
> > Thanks,
> > Dave- Hide quoted text -

>
> - Show quoted text -


Yes .. I've tried both that and a full back fill. With the quota
backfill I've tried all the available options and the same result
occurs with all.

Thanks
Dave

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

On Feb 22, 11:09 pm, "Dave" <floy...@gmail.com> wrote:
> On Feb 22, 6:29 am, NSM Development <storagemana...@novell.com> wrote:
>
>
>
>
>
> > Dave,
> > Which backfill are you doing? Are you using the quota backfill?

>
> > thanks,
> > NSM Development

>
> > Dave wrote:
> > > Hi guys

>
> > > I recently did a backfill on an entire container to ensure all users
> > > had a home dir.

>
> > > I have a quota of 40mb applied to that container's policy.

>
> > > I also have a few groups in the container that have another policy
> > > associated so I can up the quota on the users in those groups. One of
> > > those is a "Quota Unlimited" group, which has an initial quota of 0.

>
> > > The backfill on the container naturally reset all users to 40mb.

>
> > > So, I went to do another backfill on those groups so the higher quota
> > > would be reapplied but it's not working.

>
> > > The results screen, for each member of the group, says
> > > "No action because of current 40 meg quota. Policy is 40 meg"

>
> > > HELP!
> > > I've amended the policy to have a 5000 mb quota instead of unlimited,
> > > and done another backfill, same result.

>
> > > I just tried the same thing on another group and getting the same thing.

>
> > > Also, the policy has quota manager enabled with no maximum set.. so as
> > > a workaround, I went into quota manager for one of the users but it's
> > > saying there is a 200 mb limit, so i can't increase the quota that way.

>
> > > So, I currently have users who can't save to their home directories
> > > because the quota isn't being applied.

>
> > > What's going wrong here?

>
> > > Thanks,
> > > Dave- Hide quoted text -

>
> > - Show quoted text -

>
> Yes .. I've tried both that and a full back fill. With the quota
> backfill I've tried all the available options and the same result
> occurs with all.
>
> Thanks
> Dave- Hide quoted text -
>
> - Show quoted text -


Hey guys, any ideas for me on the quota issue?
I also noticed something strange today - one of my policies wasn't
associated to any containers. Bit weird as I didn't remove the
association, and no-one else has access to NSM, so it just disappeared
by itself. I re-associated it and did a back fill to fix all the
missed users and it seems fine, but it worries me that it was somehow
not associated any more.

I also experienced an abend when trying to do routine stuff within NSM
Admin. This has happened twice now in the past week.

And finally, any idea on when we'll have a search ability ? It takes
me quite literally up to 10 minutes to find a user account in NSM
Admin as you have to wait for it to scan the entire container before
all the users are available in the list. I have 25,000 user objects
in one container!

REgards
Dave
***************************************************************

Abend 1 on P01: Server-5.70.05: Page Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 9AD3E4FF EBX = 8D76C34E ECX = 2C460300 EDX = 9A9D0980
ESI = 000045F7 EDI = 9BBCE500 EBP = A610D047 ESP = 9D124B20
EIP = 6376502F FLAGS = 00010086
6376502F 6F OUTSD
EIP in UNKNOWN memory area
Access Location: 0x000045F7

The violation occurred while processing the following instruction:
6376502F 6F OUTSD
63765030 726B JB 6376509D
63765032 7374 JNB 637650A8
63765034 61 POPAD
63765035 7469 JZ 637650A0
63765037 6F OUTSD
63765038 6E OUTSB
63765039 2800 SUB [EAX], AL
6376503B 0000 ADD [EAX], AL
6376503D 2E52 CS:
PUSH EDX



Running process: httpexpThread29 Process
Thread Owned by NLM: HTTPSTK.NLM
Stack pointer: 9D124B10
OS Stack limit: 9D11CC40
CPU 1 (Thread 9AD3E440) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 5050090 Wait for interrupt
Stack: --9BBCE500 ?
--63760060 ?
--65646956 ?
--6E69576F ?
--72616A2E ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)

Additional Information:
The CPU encountered a problem executing code in SERVER.NLM. The
problem may be in that module or in data passed to that module by a
process owned by HTTPSTK.NLM.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

Dave,
I have a few questions for you.

Are the quotas _not_ being applied on any server or only this one in
particular? If yes, is it on one volume versus others on this same server?

If yes, check the volume with NSSMU, and make sure that directory quotas
are enabled for this particular volume. Is it enabled?

Are you able to set the quota with ConsoleOne or iManager?

thanks,
NSM Development

Dave wrote:
> On Feb 22, 11:09 pm, "Dave" <floy...@gmail.com> wrote:
>> On Feb 22, 6:29 am, NSM Development <storagemana...@novell.com> wrote:
>>
>>
>>
>>
>>
>>> Dave,
>>> Which backfill are you doing? Are you using the quota backfill?
>>> thanks,
>>> NSM Development
>>> Dave wrote:
>>>> Hi guys
>>>> I recently did a backfill on an entire container to ensure all users
>>>> had a home dir.
>>>> I have a quota of 40mb applied to that container's policy.
>>>> I also have a few groups in the container that have another policy
>>>> associated so I can up the quota on the users in those groups. One of
>>>> those is a "Quota Unlimited" group, which has an initial quota of 0.
>>>> The backfill on the container naturally reset all users to 40mb.
>>>> So, I went to do another backfill on those groups so the higher quota
>>>> would be reapplied but it's not working.
>>>> The results screen, for each member of the group, says
>>>> "No action because of current 40 meg quota. Policy is 40 meg"
>>>> HELP!
>>>> I've amended the policy to have a 5000 mb quota instead of unlimited,
>>>> and done another backfill, same result.
>>>> I just tried the same thing on another group and getting the same thing.
>>>> Also, the policy has quota manager enabled with no maximum set.. so as
>>>> a workaround, I went into quota manager for one of the users but it's
>>>> saying there is a 200 mb limit, so i can't increase the quota that way.
>>>> So, I currently have users who can't save to their home directories
>>>> because the quota isn't being applied.
>>>> What's going wrong here?
>>>> Thanks,
>>>> Dave- Hide quoted text -
>>> - Show quoted text -

>> Yes .. I've tried both that and a full back fill. With the quota
>> backfill I've tried all the available options and the same result
>> occurs with all.
>>
>> Thanks
>> Dave- Hide quoted text -
>>
>> - Show quoted text -

>
> Hey guys, any ideas for me on the quota issue?
> I also noticed something strange today - one of my policies wasn't
> associated to any containers. Bit weird as I didn't remove the
> association, and no-one else has access to NSM, so it just disappeared
> by itself. I re-associated it and did a back fill to fix all the
> missed users and it seems fine, but it worries me that it was somehow
> not associated any more.
>
> I also experienced an abend when trying to do routine stuff within NSM
> Admin. This has happened twice now in the past week.
>
> And finally, any idea on when we'll have a search ability ? It takes
> me quite literally up to 10 minutes to find a user account in NSM
> Admin as you have to wait for it to scan the entire container before
> all the users are available in the list. I have 25,000 user objects
> in one container!
>
> REgards
> Dave
> ***************************************************************
>
> Abend 1 on P01: Server-5.70.05: Page Fault Processor Exception (Error
> code 00000000)
>
> Registers:
> CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
> EAX = 9AD3E4FF EBX = 8D76C34E ECX = 2C460300 EDX = 9A9D0980
> ESI = 000045F7 EDI = 9BBCE500 EBP = A610D047 ESP = 9D124B20
> EIP = 6376502F FLAGS = 00010086
> 6376502F 6F OUTSD
> EIP in UNKNOWN memory area
> Access Location: 0x000045F7
>
> The violation occurred while processing the following instruction:
> 6376502F 6F OUTSD
> 63765030 726B JB 6376509D
> 63765032 7374 JNB 637650A8
> 63765034 61 POPAD
> 63765035 7469 JZ 637650A0
> 63765037 6F OUTSD
> 63765038 6E OUTSB
> 63765039 2800 SUB [EAX], AL
> 6376503B 0000 ADD [EAX], AL
> 6376503D 2E52 CS:
> PUSH EDX
>
>
>
> Running process: httpexpThread29 Process
> Thread Owned by NLM: HTTPSTK.NLM
> Stack pointer: 9D124B10
> OS Stack limit: 9D11CC40
> CPU 1 (Thread 9AD3E440) is in a NO SLEEP state
> Scheduling priority: 67371008
> Wait state: 5050090 Wait for interrupt
> Stack: --9BBCE500 ?
> --63760060 ?
> --65646956 ?
> --6E69576F ?
> --72616A2E ?
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
> --00000000 (LOADER.NLM|KernelAddressSpace+0)
>
> Additional Information:
> The CPU encountered a problem executing code in SERVER.NLM. The
> problem may be in that module or in data passed to that module by a
> process owned by HTTPSTK.NLM.
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

I only have three servers that have storage with quotas. I don't seem
to be having an issue on the two remote sites, just the big central
one.

Yes, directory quotas are enabled. It's not that quotas aren't
working, it's that enforcing the policy isn't.

The error I'm getting is that NSM isn't even trying to set the quota,
because it detects a 40mb quota on the users already, and the policy
is set to 40mb. However that's not the case, the policy has a 100mb
quota (for instance).

cheers
Dave

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

On Mar 2, 6:03 pm, "Dave" <floy...@gmail.com> wrote:
> I only have three servers that have storage with quotas. I don't seem
> to be having an issue on the two remote sites, just the big central
> one.
>
> Yes, directory quotas are enabled. It's not that quotas aren't
> working, it's that enforcing the policy isn't.
>
> The error I'm getting is that NSM isn't even trying to set the quota,
> because it detects a 40mb quota on the users already, and the policy
> is set to 40mb. However that's not the case, the policy has a 100mb
> quota (for instance).
>
> cheers
> Dave


Hellooooooo anyone out there? 🙂
Help!


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

Dave,
Based on the fact that it's working on other machines, but not this one.
It sounds like you are going to have to go through the NSS pool rebuild
processes. I suggest a working with NTS to get your NSS pool back into
shape.

thanks,
NSM Development

Dave wrote:
> I only have three servers that have storage with quotas. I don't seem
> to be having an issue on the two remote sites, just the big central
> one.
>
> Yes, directory quotas are enabled. It's not that quotas aren't
> working, it's that enforcing the policy isn't.
>
> The error I'm getting is that NSM isn't even trying to set the quota,
> because it detects a 40mb quota on the users already, and the policy
> is set to 40mb. However that's not the case, the policy has a 100mb
> quota (for instance).
>
> cheers
> Dave
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: quota not being applied

On Mar 8, 12:39 am, NSM Development <storagemana...@novell.com> wrote:
> Dave,
> Based on the fact that it's working on other machines, but not this one.
> It sounds like you are going to have to go through the NSS pool rebuild
> processes. I suggest a working with NTS to get your NSS pool back into
> shape.
>
> thanks,
> NSM Development
>
>
>
> Dave wrote:
> > I only have three servers that have storage with quotas. I don't seem
> > to be having an issue on the two remote sites, just the big central
> > one.

>
> > Yes, directory quotas are enabled. It's not that quotas aren't
> > working, it's that enforcing the policy isn't.

>
> > The error I'm getting is that NSM isn't even trying to set the quota,
> > because it detects a 40mb quota on the users already, and the policy
> > is set to 40mb. However that's not the case, the policy has a 100mb
> > quota (for instance).

>
> > cheers
> > Dave- Hide quoted text -

>
> - Show quoted text -


I can't see why the problem would be NSS Pool related. The pool is
functional with no errors. The error is that NSM isn't even trying to
set the group assigned quota at all. The container applied quota is
working fine.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.