# Best practices for mounting disk

**URL:** <https://forums.suse.com/t/best-practices-for-mounting-disk/17821>\
**Category:** k3s, k3OS, and k3d\
**Created:** [June 25, 2020, 3:27pm UTC](https://forums.suse.com/t/best-practices-for-mounting-disk/17821 "2020-06-25T15:27:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gbonnefille](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gbonnefille/32/6581_2.png) [@gbonnefille](https://forums.suse.com/u/gbonnefille)\
**Post date:** [June 25, 2020, 3:27pm UTC](https://forums.suse.com/t/best-practices-for-mounting-disk/17821/1 "2020-06-25T15:27:35Z")

</div>

Hi,

In order to run K3OS in production, I’m looking for a best practices to mount a disk for storage.

My K3OS will be single node. So I plan to use local-path storage for volume provisioning. This node will host more and more services, so I fear to have to extend the disk space in the future.  
So I decided to:

- use two disks: one for system and one for data
- as the data will grow, and due to _hyper-converged_ approach of our internal cloud solution, the effective disk cannot grow directly and we can only provision more disks, so LVM2.

In config.yaml I activated LVM2:

```auto
 boot_cmd:
  - "vgscan"
  - "vgchange -a y"

```

The ❓ is: how should I mount this LVM2 volume in config.yaml?

- should I directly run the `"mount /dev/data/storage /var/lib/rancher/k3s/storage"`?
- should I patch the `/etc/fstab` with `"echo /dev/data/storage /var/lib/rancher/k3s/storage ... > /etc/fstab"`?
- any other option?

---

<div class="post-metadata">

**Author:** ![MIG](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mig/32/7038_2.png) [@MIG](https://forums.suse.com/u/MIG)\
**Post date:** [December 31, 2020, 9:41pm UTC](https://forums.suse.com/t/best-practices-for-mounting-disk/17821/2 "2020-12-31T21:41:51Z")

</div>

I’ve got the same question. Did you ever find an answer or at least something that worked? I tried making a mount for in the command yaml. Then used the write\_files to write an fstab with my nfs. That didn’t fully work. After boot I could run mount -a and it would mount my nfs share but didn’t do it automatically on boot

---

<div class="post-metadata">

**Author:** ![gbonnefille](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gbonnefille/32/6581_2.png) [@gbonnefille](https://forums.suse.com/u/gbonnefille)\
**Post date:** [March 10, 2021, 2:40pm UTC](https://forums.suse.com/t/best-practices-for-mounting-disk/17821/3 "2021-03-10T14:40:21Z")

</div>

Perhaps should you ensure NFS is started. Have a look at [Starting NFS at boot time](http://forums.suse.com/t/starting-nfs-at-boot-time/19756)