[SERVER-1180] --repair does not seem to respect --repairpath on disk space check Created: 01/Jun/10  Updated: 12/Jul/16  Resolved: 12/Jul/10

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 1.4.2
Fix Version/s: 1.5.5

Type: Bug Priority: Minor - P4
Reporter: Damon Cortesi Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

64-bit centos


Participants:

 Description   

I was attempting to repair a database on a volume with little free space left. The documentation seems to indicate that I can use --repairpath in this case for the temporary files. However, when using --repairpath to specify a different volume, I still got an error message about a lack of disk space, as shown below:

$ sudo mongod --dbpath /srv/mongodb/data --repairpath /tempdrive/ --repair

Tue Jun 1 04:25:29 need to upgrade database dbname with pdfile version 4.5, new version: 4.5
Tue Jun 1 04:25:29 starting upgrade
Tue Jun 1 04:25:29 dbname repairDatabase dbname
Tue Jun 1 04:25:29 dbname Cannot repair database dbname having size: 124443951104 (bytes) because free disk space is: 12333137920 (bytes)
Tue Jun 1 04:25:29 dbname Assertion failure doDBUpgrade( dbName , errmsg , h ) db/db.cpp 374



 Comments   
Comment by auto [ 12/Jul/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1180 fix baseName
http://github.com/mongodb/mongo/commit/4226a40814315c804183c96c95623eb3d0d25fec

Comment by auto [ 12/Jul/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1180 try to fix header non osx
http://github.com/mongodb/mongo/commit/746e1e80db9451d91625c47cfb5d36d92ca4e9c8

Comment by auto [ 12/Jul/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1180 check free space in repair path
http://github.com/mongodb/mongo/commit/7e6a0635292857cb303d147504be6a90b4cbf5e7

Generated at Thu Feb 08 02:56:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.