[SERVER-14137] db stats Created: 03/Jun/14  Updated: 17/Oct/14  Resolved: 17/Oct/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.4.9
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jack Wang Assignee: Ramon Fernandez Marina
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-15369 explicitly zero .ns files on creation Closed
Related
Operating System: ALL
Participants:

 Description   

r1:SECONDARY> db.stats();

{ "ok" : 0, "errmsg" : "missing ns: \u0001" }

 Comments   
Comment by Ramon Fernandez Marina [ 17/Oct/14 ]

After examining more .ns files for installation that exhibit the behavior reported in this ticket we're going to close this ticket as a duplicate of SERVER-15369, as the error produced from db.stats() was caused by the namespace file corruption caused by buggy implementations of SCSI WRITE SAME (see SERVER-15369 for more information).

Comment by Iago Gonzalez [ 06/Oct/14 ]

Hi Ramón,
Yes, i'm running a Ubuntu 12.04.3 LTS (GNU/Linux 3.8.0-29-generic x86_64) on a Vmware enviroment (ESXi 5.5)
For security purposes, I prefer to not upload the ns file because I don't know if the ns file could expose critical data.

Regards,
Iago

Comment by Ramon Fernandez Marina [ 06/Oct/14 ]

jackwang, iagogonzalez@ipglobal.es, if you're still seeing errors when running db.stats(), would it be possible for you to upload your .ns files? In SERVER-15369 we're seeing similar errors on some Linux systems running on VMWare – are you running this combination? If so, could you provide the distribution name and version, the kernel version, and the VMWare product/version you're using?

Thanks,
Ramón.

Comment by Ramon Fernandez Marina [ 03/Oct/14 ]

This could be an instance of SERVER-15369. Please tune in to that ticket for further updates.

Comment by Iago Gonzalez [ 11/Jun/14 ]

Hello,
I have the same problem with the same version of (2.4.9). In a replica set, in the primary:

ne:PRIMARY> db.stats()

{ "ok" : 0, "errmsg" : "missing ns: 7d34dedf32e13523a8c5f16674" }

The secondary gives me ok the stats. I did a mongodump and mongorestore to one Standalone server and then I create the Replica Set with one Seconday and an Arbiter.

The collections give me the stats correctly

Regards

Comment by Ramon Fernandez Marina [ 03/Jun/14 ]

I'm unable to reproduce this error message:

MongoDB shell version: 2.4.9
connecting to: test
replset:SECONDARY> db.stats();
{
        "db" : "test",
        "collections" : 0,
        "objects" : 0,
        "avgObjSize" : 0,
        "dataSize" : 0,
        "storageSize" : 0,
        "numExtents" : 0,
        "indexes" : 0,
        "indexSize" : 0,
        "fileSize" : 0,
        "nsSizeMB" : 0,
        "dataFileVersion" : {
 
        },
        "ok" : 1
}

Note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag.

If you can provide more information on how to reproduce the behavior you describe please feel free to add it to the ticket and reopen it, but for a question like this involving more discussion it would be best to post on the mongodb-users group.

Generated at Thu Feb 08 03:33:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.