I have a 250GB external hard drive which used to be FAT32 formatted, which i use to backup all the Music and Pictures i have on my drive. This is so that i have a copy of it incase i reinstall or change installations so that i can easily copy files across, and for safety.
I think formatting it to EXT3 and giving it a mount pount, like /store would be beneficial as i only use it for Linux.
My questions are:
Is formatting it to EXT3 beneficial?
If it gets a mount point, like /store and the entry is written to fstab, will it need to be plugged in every time i turn the PC on, or will it just not mount that partition?
will i have a problem with permissions as /store would appear under /root.
Could i do automated backups to a drive like this easier than if it were FAT32?
Is there a better solution to this?
I appreicate i am asking alot, i just dont want to mess this up as i rely on it for all my files.
Thanks for the quick replies. I think last night when i was formatting it i gave it a mount point of /store. I’ll reformat tonight and it will hopefully remove it from fstab.
/etc/fstab is only changed if you were doing the formatting from the running SUSE system in Yast - Partitioner?!
I take it that’s what you did?
Actually, there shouldn’t be a problem with what you did. Only you might not have the right permissions, but that can be changed.
Yeah thats exactly right. I think you helped me last week with my partitioning (many many thanks) and i ended up installing a /boot partition, and the rest of the disk as LVM (so /root, swap, /home, /files) as whenever i made /root and swap physical partitions and added a LVM, on reboot after a kernel upgrade it couldnt read /home!
I used Yast and formatted the external drive, and assigned /store as a mount point, thinking this would allow me to use it like a physical drive to backup my data to.
On exiting, it asked me if i wanted to write the changes to fstab, clicked yes and away i went.
Don’t forget to use tune2fs to decrease the size of reserved space though, or you could easily be wasting 25gigs of space!
I always use reiserfs instead, it seems to run a lot smoother, and doesn’t force entire disk checks after 30 mounts. Something that will get VERY boring very quickly on removable devices.
Plus if you accidentally unplug the drive without unmounting it, it will be automatically checked the next time you plug it in, but it only takes a few seconds compared to ext3!
I’ve been using reiserfs for ALL my partitions since about 2004 and never had a single problem.
Apologies for my ignorance, what does the tune2fs application do? And how would i apply it to my situation. I’ll go away and google it, but it would really help me to have it explained.
This is where we differ in opinion. When the disk is always connected, there is no reason why a so called external disk would be handled different from a so called inetrnal disk.
With fstab you can mount it where you want/need it (which is one of those big winners compaired to MS). In this case I would prefer a mount point like /home/<user>/music-pictures/.
As opposed to HAL which will only mount indside /media/ (and only for one of the users that is accidently loged in) which imho is OK for much changing plug in/remove devices and not for something you want be part of your system.
But as said it is my personal opinion and I have allready found it is often not understood by those infected by years of MS usage rotfl!
If not, fstab will bring you no benefit, because you can not set “auto” in fstab and will have to mount it by hand, or you will run into trouble the disk is not connected at boot time.
No problem.
a) Disk has a disklabel <SOME_FANCY_NAME>
b) Hal/udev will always mount it to /media/<SOME_FANCY_NAME>
If the disk is not connected, the link is “dead” but does no harm, if it is connected, it will be accessible via /media or your own, unique “mountpoint”.
Maybe, but the above solution is very “unix-like”.
An yes, when it is only connected occasionaly, follow Akoellhs advice. Specialy the symbolioc link is usefull because you then “have it where you want/need it”.
Nice guys these IT geeks. They say **Volume **label, they mean **Disk **label for what is in fact a **Partition **label rotfl!
And not even that because it belongs to the File System.