Home / ubuntu / Questions / 789449
Accepted
Alexander Zeitler
Asked: 2016-06-21 12:07:43 +0800 CST

chown doesn't work permanently

  • 772

I've set up a Ubuntu Server 14.04 instance including Mate Desktop in AWS EC2. It has a 30GB system volume and a 80GB volume which is available at /mnt.

After calling sudo chown <awsuser> /mnt I can create files and folders on the 80GB volume.

After rebooting the VM I have to re-run sudo chown <awsuser> /mnt otherwise I get a permission denied error.

How can I make sudo chown <awsuser> /mnt permanent?

Update: Output of mount | grep /mnt:

/dev/xvdb on /mnt type ext3 (rw)

Output of ls -ld /mnt

drwxr-xr-x 3 root root 4.0K Nov 23  2015 /mnt
14.04

2 Answers

  1. Best Answer

    /mnt points to an instance storage. Instance storage is tied to the instance lifecycle as pointed out in the docs:

    http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html#instance-store-lifetime

    You can specify instance store volumes for an instance only when you launch it. The data in an instance store persists only during the lifetime of its associated instance. If an instance reboots (intentionally or unintentionally), data in the instance store persists. However, data in the instance store is lost under the following circumstances:

    • The underlying disk drive fails
    • The instance stops
    • The instance terminates

    Therefore, do not rely on instance store for valuable, long-term data. Instead, you can build a degree of redundancy (for example, RAID 1/5/6), or use a file system (for example, HDFS and MapR-FS) that supports redundancy and fault tolerance. You can also back up data periodically to more durable data storage solutions such as Amazon S3 or Amazon EBS.

    • 3

  2. After sudo chown <awsuser> /mnt

    chattr -i /mnt

    It makes changes permanent and revertible only by root.

    • 0