Nope
You should not use space in the Label. It just creates issues as you would have to “escape” them every time
Nope
You should not use space in the Label. It just creates issues as you would have to “escape” them every time
Argh, LINUX!
Is it okay to use CAPITAL letters?
Yes, you also can use _
.
No problem to use space you just would need to escape it with \
Thanks for the quick reply.
I just used:
mkfs.ext4 /dev/sda1 -T largefile4 -m 1 -L SeagateBackupPlus8TB
Then I get:
Warning: label too long; will be truncated to 'SeagateBackupPlu'
Great now I need to rename it!
But I don’t see it in df:
osmc@osmc:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 774688 0 774688 0% /dev
tmpfs 899236 16876 882360 2% /run
/dev/vero-nand/root 14499760 10138932 3601228 74% /
tmpfs 899236 0 899236 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 899236 0 899236 0% /sys/fs/cgroup
tmpfs 179844 0 179844 0% /run/user/1000
Did you reboot or unplug/replug?
No, just did a:
e2label /dev/sda1 Seagate8TB
Do I need to reboot to automount?
Well you need to trigger an action either reboot or unplug/replug
Okay, got it after ‘reboot’.
/dev/sda1 7811937256 94236 7733686384 1% /media/Seagate8TB
Used space looks better now.
How much space was used after you formatted to ext4?
osmc@osmc:~$ df
Filesystem 1K-blocks Used Availabl Use% Mounted on
/dev/sda1 7811937256 94236 7733686384 1% /media/Seagate8TB
What did you use to format the drive?
I tried to format my 8tb seagate and its using 117gb after format so ended up formatting in exfat
But then again I haven’t got a clue what I’m doing
Tried following what’s been posted in this thread, but just doesn’t to work for me
He formatted using OSMC, he showed all the commands he used
But be careful, using that command would nuke all your data on the first connected drive
Someone correct me if i’m wrong, but doesn’t exfat have some issues with OSMC and carry the same performance hit as ntfs?
exFAT will perform better than NTFS (it’s still a userland driver) but worse than EXT4. It’s a good compromise for people who need to move a drive between Windows and linux.
The samba issues still exist though don’t they?
The network protocol performance is separate from the drive performance. Of course, poor drive performance will appear to affect network performance. And poor network performance will appear to affect drive performance. But they are different. It can be difficult sometimes to find a bottleneck in these cases. Using something like dd to copy files locally and then to the same drive over the network can help find where the performance issue is. If all access is linux to linux then the best combination will always be NFS/EXT4.
I was actually referring to failing large file transfers and no status when transferring to/from an exFat formatted drive connected to OSMC over a samba connection. With a failed transfer being a bigger issue when being done to a non journaled file system.
Like I said, finding issues like this are best done with testing with a tool like dd. Run dd on the host (assuming it’s not windows) and create a large file on the drive. Then do the same test over the network from the client. On a network mounted drive, the client does not know how the drive is formatted. The host handles those details.
I meant did he use putty or gparted?