Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Messages in /nsr/logs/daemon.log Storage Node NSR 7.6.3

Status
Not open for further replies.
v1nsr

v1nsr

Technical User
Oct 4, 2012
50
0
0
QA
I'm seeing a huge number of entries being generated and written into /nsr/logs/daemon.log on one of our storage nodes (ktlwgbak101 - Redhat EL 6) - so many that the log is growing to 10GB+ in a couple of days.


A few lines displaying entries are below:

01/28/13 14:15:36 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 20192
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 32768
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 12588
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 20100
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 32768
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 12680
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 20008
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 32768
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 12772
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 19916
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 32768
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 12864
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 19824
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 32768
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 12956
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: len = 19732
01/28/13 14:15:37 2 719808256 ktlwgbak101.grpitsrv.com nsrmmd filesys_chunk: used = 180 TB for volume DDBoost.004.



Please advise .
 
Sort by date Sort by votes
IMHO these are informational messages - i am pretty sure logging them does not make sense. You better get in touch with EMC support to sort this out.

To start a new log file you should wait for an idle data zone and restart the client daemon on the SN.
 
Upvote 0 Downvote
Hi

Can you please advise as how we can check the NSR_MAXLOGSIZE on the server ?? for the existing daemon.log . I want to know for both unix and windows .
 
Upvote 0 Downvote
I have to look this up myself.
But it does not really make sense as you must restart the services to trigger NW to create a new file.

What you really need is to update to 8.0+ where NW can start a new file without restarting the services.

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

anil5555
  • Locked
  • Question
Networker in HA ( High availability ) for DR
Replies
0
Views
114
anil5555
anil5555
Robert Lee
  • Locked
  • Question
Rubber roller of Onstream drives have turned to goo in 2020.
Replies
7
Views
175
edfair
edfair
Marino.
  • Locked
  • Question
Restore backup in Open VMS
Replies
0
Views
113
Marino.
Marino.
Hondo008
  • Locked
  • Question
NSR Scripts for Importing Multiple directories to Client Save Sets
Replies
0
Views
41
Hondo008
Hondo008
Karan7799
  • Locked
  • Question
How to check the Daemon.log file for troubleshooting
Replies
1
Views
53
605
605

Part and Inventory Search

Sponsor

Back
Top