You can copy the lines started with /dev/sd**
from mtab (/etc/mtab
) and paste them in to a new text file and change /dev/sd**
with UUID
or LABEL
.
For example from your config:
use
UUID="3fc55e0f-a9b3-4229-9e76-ca95b4825a40" / ext4 rw,errors=remount-ro 0 0
instead
/dev/sda1 / ext4 rw,errors=remount-ro 0 0
The line above also works, but UUID
is the new standart and if your grub configured with UUID
, it might can't understand which partition is what.
if partition has Label you can use the LABEL
instead UUID
, for example:
LABEL="Files_Server_Int" /media/Files_Server ext4 rw 0 0
IMO copy your mtab to a new file and remove the lines started with "none"
and change the /dev/sd**
part with blkid output equivelants. If UUID exist, use the UUID
instead of /dev/sd**
. If LABEL exist use the LABEL
instead of UUID.
Do not remove anything else except "none"
lines. Save the file, change the file name to fstab
and copy in to /etc
.
Finally add lines for swap
if any (if you forget this, your system will boot but you might have zero swap space or swap file will be generated at root (/
) depending of OS default configuration.). e.g. in your case note that blkid
prints this line:
/dev/sda5: UUID="718e611d-b8a3-4f02-a0cc-b3025d8db54d" TYPE="swap"
so you need this line in fstab
:
UUID=718e611d-b8a3-4f02-a0cc-b3025d8db54d none swap sw 0 0
This might help to restore your fstab.
Are you running a 64-bit system? Journaling is automatically enabled on 64-bit systems as of Mongo 1.9.2, and this can take up quite a bit of space. You can safely disable journaling and clear out the old journal files (which can be quite big).
To disable from config file, you will need to COMMENT OUT or DELETE the line that says journal = true
(if it exists) and add a line that says nojournal = true
. Or, if you're running Mongo via command line, specify --nojournal
. Regardless, make sure you restart Mongo before going to the next step.
To delete the journal files, go to your {dbpath}/journal
and remove the entire journal
subdirectory. This will clear out the journal files and should clean up quite a bit of space.
Hope this helps!
Best Answer
The instance-storage (i.e. ephemeral storage) is provided as two devices on the m1.large - /dev/sdb and /dev/sdc - each of approximately 420GB. Only one of these (/dev/sdb) is mounted (to the /mnt location). While the additional volume (/dev/sdc) is available, you will need to format it before mounting it.
See: http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?instance-storage-concepts.html for the specifics of how instance-storage is allocated by instance type.
Some AMIs may not provide the full ephemeral storage, however, you can add it when launching the instance by specifying the ephemeral disk mappings in your launch command:
Where
ephemeral0
represents the root volume,ephemeral1
represents swap space, andephemeral2+
represent the remaining available ephemeral storage as per the document above.