Cannot mount an existing EBS on AWS

Question

I understand that a MTU is defined in struct net_device, and (if I'm correct) that MTU is defined on a per-device basis.

Is there a way to get a minimum packet size? I know there are clear cut definitions for e.g. IPv4, but in this case it would depend on the network interface, right?

Also, some drivers allocate an skb before receiving a packet. In this case, if the driver implements change_mtu, what happens to the skb that has already been allocated? Does it simply get destroyed and then the driver would allocate a new skb to reflect the changed MTU?

Solution 1

Looks like you have partitioned that block device. In this case, you need to mount /dev/xvdf1, not just /dev/xvdf.

Solution 2

For me there was some mysterious file causing this issue.

First check your partitions to make sure you are running an ext3 volume and then:

For me I had to clear the directory using the following command.

sudo mkfs -t ext3 /dev/sdf

Warning: this might delete files you have saved. So you can run ls to make sure you don't lose important saved files

Comments

[Sai]

Seems to work. Will update in few minutes. Thanks for this.

[Mootmoot]

Yes. Even if attached as "xvdf" using AWS Dashboard, must mount as xvdf1. To tell if you have a partitioned drive, check /dev: ls /dev/xvdf* and if so, you will see more than one entry.

[EEAA]

@Rubistro That only applies if you've partitioned the block device.

[chamberlainpi]

This literally saved my job (probably). It's odd that the Amazon AWS documentation doesn't make mention of this on this page - aws.amazon.com/articles/5213606968661598.

[Justin Fortier]

This can be absolutely destructive if you are not running an ext3 volume. You can also encounter OP error if you have picked the wrong fs type. For example if you try mount an ext4 volume as an ext3 volume. Heads up before someone deletes their data!

[ScottyBlades]

@JustinFortier, does the edit make it safer, or is there anything else that should be mentioned?

[Justin Fortier]

thanks, would suck if someone blindly copied and pasted that without checking first. Especially since OPs output log mentions ext4.