[SERVER-12375] Improper file access Created: 16/Jan/14 Updated: 10/Dec/14 Resolved: 03/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bill Shipman | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | database.cpp, files,, server | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux stsia0408 2.6.34-12-desktop #1 SMP PREEMPT x86_64 x86_64 x86_64 GNU/Linux (suse) |
||
| Operating System: | Linux |
| Steps To Reproduce: | unknown |
| Participants: |
| Description |
|
Attempting to use a db with approximately 50 collections using 604GB of disk space. Running db.stats() abruptly fails along with clients going into a "waiting" state. /var/log/mongodb/mongo.log includes the line: That file doesn't exist: mongodb@stsia0408:/var/log/mongodb> ls /var/lib/mongodb/preannotation.30* Wed Jan 15 17:06:30.062 [initandlisten] MongoDB starting : pid=15707 port=27017 dbpath=/var/lib/mongodb 64-bit host=stsia0408 Wed Jan 15 17:06:30.073 [initandlisten] journal dir=/var/lib/mongodb/journal |
| Comments |
| Comment by Thomas Rueckstiess [ 03/Jul/14 ] |
|
Hi Bill, as mentioned I'm resolving this as "cannot reproduce" since we don't have enough information to diagnose. Please feel free to re-open the issue if this should happen again. Thanks, |
| Comment by Thomas Rueckstiess [ 26/Jun/14 ] |
|
Hi Bill, Thanks for your additional input. Unfortunately, without any more details it's hard to track down the issue. Has this happened again since? If not, I think we have to mark the ticket as "cannot reproduce" for now, and you can re-open it if the problem appears again and you are able to collect fresh information. Thanks, |
| Comment by Bill Shipman [ 26/Jun/14 ] |
|
It seems like we ran the repair tool maybe twice and it cleared it up. At this point I don't clearly recall what we did. Looking in my email from January it looks like we first ran a repair and then a ? mongodump repair ? No nothing should have purged that file, it's in a limited access file tree on a machine with only 3 users in total. Myself, another programmer and the sysadmin. It is configured as a high availability replication cluster so that would have been the only thing migrating data other than a few (<10) processes doing inserts on the master but those are heavy loads. |
| Comment by Thomas Rueckstiess [ 26/Jun/14 ] |
|
Hi Bill, Sorry for the delay on this issue. It appears that the file /var/lib/mongodb/preannotation.304 was deleted somehow, as it doesn't show up on the ls anymore. I'm not aware of any reports of files being deleted due to a bug caused by MongoDB. Are you aware of anything that could have deleted the file? Any data migration, permission issues etc? Have you recovered from this situation since reporting this? Regards, |