Which is the better filesystem for a non-raid (single Data HD) setup, btrfs or ext4?
a better filesystem?
-
- OMV 3.x
- rals2007
-
-
-
thank you for the reply
One more thing...
if ever i decide btfrs as my filesystem which is still under development, can i simply just "update" it with a cli command/gui if a better "stable" one comes out later on without destroying the existing filesystem and start from scratch again? -
-
Be carreful!
If OMV is booting in FAT32 partition (/boot).
The OS is running is ext 4 (/)
You can create a BTRFS partition without incident for your data but it's another partition.Don't forget that ext4 is very good for OMV filesystem and BTRFS for NAS Datas.
-
thats what i meant, btrfs filesystem for the storage data and leave the OMV HD filesystem as default.
My setup is:
128gb SSD for OMV system.
4TB HD for storage -
thats what i meant, btrfs filesystem for the storage data and leave the OMV HD filesystem as default.
My setup is:
128gb SSD for OMV system.
4TB HD for storageOK, sorry If I didn't understood before
.
I don't know but I think we don't have to reformat for updating BTRFS.
They update sometimes BTRFS but we don't need to reformat.Don't forget it's always better for make a bakup.
You could check the BTRFS changelog here.
-
-
thank you so much for all the help & info Judibet. Backing up the data and will do btrfs
-
If you dont need snapshoting,or any of the pluses of BTRFS,i would say go with EXT4.
-
i just want to savour btrfs
-
-
Yes,btrfs is interesting. You can just view it as ZFS for Linux by Linux. Just dont use for now Raid5,6
-
so after creating btrfs, /etc/fstab now shows it as:
it used to be:Is this correct?
It seems the location is somewhat changed from /media to /srv
-
Hello,
For me, its /dev/disk/...
Like you.But yes, you could use the disk UUID.
Only one thing is bad.
The destination /media/af6e6a5c-6392-4584-a524-1a479a6524a6 exist????Ensure with blkid to check is the UID is good and ls if /media/af6e6a5c-6392-4584-a524-1a479a6524a6 exist.
Don't use this script if you are not sure or your UID, mountpoint and /etc/fstab content!
Bash: add2fstab.shif [ ! -d /media/af6e6a5c-6392-4584-a524-1a479a6524a6 ]; then echo -e "This directory didn't exist!\n"; exit 1; else echo -e "It's OK, this directory exist!\n"; cp /etc/fstab /etc/fstab.bak echo -e "\nUUID=af6e6a5c-6392-4584-a524-1a479a6524a6 /srv/dev-disk-by-label-MediaHD btrfs defaults,nofail 0 2\n" >> /etc/fstab mount /srv/dev-disk-by-label-MediaHD fi
For information:
Bash: /etc/fstab/dev/disk/by-label/MediaHD fstype /srv/dev-disk-by-label-MediaHD none bind,nofail 0 2
Equal:
-
-
Is this correct?
It seems the location is somewhat changed from /media to /srv
Yes this is correct. OMV doesn't use UUIDs anymore since they may be duplicated with LVM snapshots. The default mounting location changed in 3.0.67 (I think) to /srv.
-
The destination /media/af6e6a5c-6392-4584-a524-1a479a6524a6 exist????
It doesnt exist. thats the old value written in fstab.i wrote it down before converting it to BTRFS
Yes this is correct. OMV doesn't use UUIDs anymore since they may be duplicated with LVM snapshots. The default mounting location changed in 3.0.67 (I think) to /srv.
Great! Thanks for the info
So does this mean I'm all good?
-
Could you send us your /etc/fstabl content, please?
You need to make no error on it. -
-
Old FSTAB (Storage HD is EXT4)
Code# <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdc1 during installation UUID=623ec8c1-d525-4b4f-be5c-fdcb9a31c1a6 / ext4 errors=remount-ro 0 1 # swap was on /dev/sdc5 during installation UUID=5ab274bb-0d42-4228-b823-cff5b3753747 none swap sw 0 0 # >>> [openmediavault] UUID=af6e6a5c-6392-4584-a524-1a479a6524a6 /media/af6e6a5c-6392-4584-a524-1a479a6524a6 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
New FSTAB (Storage HD is BTRFS)
Code# / was on /dev/sdc1 during installation UUID=623ec8c1-d525-4b4f-be5c-fdcb9a31c1a6 / ext4 errors=remount-ro 0 1 # swap was on /dev/sdc5 during installation UUID=5ab274bb-0d42-4228-b823-cff5b3753747 none swap sw 0 0 # >>> [openmediavault] /dev/disk/by-label/MediaHD1 /srv/dev-disk-by-label-MediaHD1 btrfs defaults,nofail 0 2
-
You should never edit the OMV section of fstab. It is regenerated every boot. If something is wrong, it needs to be edited in config.xml and then omv-mkconf fstab.
-
I didn't. it changed on its own after i convert my storage from EXT4 to BTRFS.
Here's what i did:
1. Backup my storaga data
2. Unmounted and created BTRFS filesystem n my storage HD
3. created shared folder as MediaHD
4, restared, then i noticed the stab changed by itself -
-
I didn't. it changed on its own after i convert my storage from EXT4 to BTRFS.
You did it the right way. I was just mentioning that in case people wanted to convert to btrfs from ext4 without unmounting/mounting from the OMV web interface.
-
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!