Highlighted
W_Prindl Absent Member.
Absent Member.
1230 views

Does anybody know, when there will be a fix for TID 7003563 NSS Volume Randomly Deactivates due to Snapshots ?

This one is a real pain if you experience it during normal working
hours - and do not know of it in advance. It would be nice to know such
show-stopping problems in advance without having to read all TIDs -
something like an alert service for show-stopping bugs.?!


--
W. Prindl

W. Prindl
Labels (2)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Does anybody know, when there will be a fix for TID 7003563 NSSVolume Randomly Deactivates due to Snapshots ?

On Wed, 22 Jul 2009 10:46:38 +0000, W_ Prindl wrote:

> This one is a real pain if you experience it during normal working hours
> - and do not know of it in advance. It would be nice to know such
> show-stopping problems in advance without having to read all TIDs -
> something like an alert service for show-stopping bugs.?!


Are you seeing this in your production environment ? If so, why not log a SR with Technical support ?
You can refer to this TID and the techie working on your SR can check the bug number that is associated with this TID.

Perhaps you can provide additional details to speed up resolution as well, and if not, the more customers that run into
the issue, the higher the pressure on engineering to provide a resolution.

Cheers
Hans
0 Likes
W_Prindl Absent Member.
Absent Member.

Re: Does anybody know, when there will be a fix for TID 7003563 NSSVolume Randomly Deactivates due to Snapshots ?

Yes it was on our Groupwise production server. Suddenly everybody
complained about Groupwise not working - and of course that is nothing
to wonder, if the volume used to store the domain and post-office data
has deactivated itself. After some search and thoughts, if that could
be a hardware issue, I found the TID mentioned, which pretty exactly
matched our situation. Now - after doing a complete disk image - I
applied the workaround to this server and to our fileserver, because
the volumes on that server had also snapshots enabled.

So till now all seems to work again - I hope this will remain so.


I did not open a SR because at the moment I only have upgrade
protection and no maintenance.

I assume, that this problem was introduced by one of the latest NSS
patches, which I applied one week before. In the past this server had
not any issues since its creation in the end of 2008.

--
W. Prindl


Hans van den Heuvel wrote:

>On Wed, 22 Jul 2009 10:46:38 +0000, W_ Prindl wrote:
>
>> This one is a real pain if you experience it during normal working
>>hours - and do not know of it in advance. It would be nice to know
>>such show-stopping problems in advance without having to read all
>>TIDs - something like an alert service for show-stopping bugs.?!

>
>Are you seeing this in your production environment ? If so, why not
>log a SR with Technical support ? You can refer to this TID and the
>techie working on your SR can check the bug number that is associated
>with this TID.
>
>Perhaps you can provide additional details to speed up resolution as
>well, and if not, the more customers that run into the issue, the
>higher the pressure on engineering to provide a resolution.
>
>Cheers
>Hans


W. Prindl
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Does anybody know, when there will be a fix for TID 7003563NSSVolume Randomly Deactivates due to Snapshots ?

On Thu, 23 Jul 2009 13:39:32 +0000, W_ Prindl wrote:

> I assume, that this problem was introduced by one of the latest NSS
> patches, which I applied one week before. In the past this server had
> not any issues since its creation in the end of 2008.


Afaict, the original customer that reported the issue has closed his service request, so he does not require a fix for this
anymore. Because if this, there does no longer seem to be any customer demand (through SR's that is) for a fix, and
resolving the issue will get a low(er) priority for engineering in resolving. (btw : The issue is not related to the latest NSS
patch)

If you can live with the workaround you applied for that long, that is good, if not, I would suggest you get your
maintenance sorted and log a SR for this, or pay for a single incident SR, which (afaict) should still be credited to your
account if this is about an unresolved issue.


Good luck with making your choice

Regards
Hans
0 Likes
W_Prindl Absent Member.
Absent Member.

Re: Does anybody know, when there will be a fix for TID 7003563NSSVolume Randomly Deactivates due to Snapshots ?

First thanks for the info on the status of the issue!

Do you by chance know to which piece of software it is related, if you
know, that it is not related to the latest NSS patch?

Despite of the fact that we will soon have maintenance, it would be
nice if the per incident support for unresolved issues and bugs was
free as before and that fact is somewhere documented, so that one can
rely upon this.


--
W. Prindl


Hans van den Heuvel wrote:

>On Thu, 23 Jul 2009 13:39:32 +0000, W_ Prindl wrote:
>
>> I assume, that this problem was introduced by one of the latest NSS
>> patches, which I applied one week before. In the past this server
>>had not any issues since its creation in the end of 2008.

>
>Afaict, the original customer that reported the issue has closed his
>service request, so he does not require a fix for this anymore.
>Because if this, there does no longer seem to be any customer demand
>(through SR's that is) for a fix, and resolving the issue will get a
>low(er) priority for engineering in resolving. (btw : The issue is
>not related to the latest NSS patch)
>
>If you can live with the workaround you applied for that long, that
>is good, if not, I would suggest you get your maintenance sorted and
>log a SR for this, or pay for a single incident SR, which (afaict)
>should still be credited to your account if this is about an
>unresolved issue.
>
>
>Good luck with making your choice
>
>Regards
>Hans


W. Prindl
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Does anybody know, when there will be a fix for TID7003563NSSVolume Randomly Deactivates due to Snapshots ?

On Fri, 24 Jul 2009 10:17:47 +0000, W_ Prindl wrote:

> First thanks for the info on the status of the issue!


Welcome

> Do you by chance know to which piece of software it is related, if you
> know, that it is not related to the latest NSS patch?


Yes, the problem is with the Copy on Write attribute as is stated in the TID

> Despite of the fact that we will soon have maintenance, it would be nice
> if the per incident support for unresolved issues and bugs was free as
> before and that fact is somewhere documented, so that one can rely upon
> this.


I don't know (if) where this is documented, but the fact remains the bug is still open without a patch available to the public.
So imo even itf it is a paid for incident, it should still be credited to you. I'm not aware the procedures on this topic have
changed recently

I'm just not wearing a Novell hat at the moment, so it may be decided otherwise.
Ultimately It's your decision to make if you wait for your maintenance, of spend the bucks for the paid incident

Cheers
Hans

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.