FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
From reading this thread, it seems that the way my external drive is mounted is causing me to get a file too large error with tar. But, my drive is automatically mounted by the OS. I know how to edit the fstab file, but what I don't know is:
1) will this over-ride the auto-mount of this USB device?
2) what is the fstab entry since I am apparently not using samba (see below)?
Here's output of commands suggested in the thread FYI:
Code:
$ strings `which tar`|grep 64
/lib64/ld-linux-x86-64.so.2
Archive contains obsolescent base-64 headers
Archive signed base-64 string %s is out of %s range
/usr/lib64
/lib64/ld-linux-x86-64.so.2
Code:
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 62890
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 1024
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Welcome to LinuxQuestions.
There is not enough information provided to say if your problem is related to the thread you posted as as reference. I would guess some type of USB drive and not a samba issue.
What version of Fedora are you running?
What type of external drive and what is its filesystem i.e. USB, eSATA and FAT32, NTFS etc. Just taking a wild guess your drive is formatted as FAT32 which has a maximum file size of 4G.
Post the complete tar command you are using.
To overcome this limit you can use tar to split the archive into smaller chunks or convert the drive to NTFS.
reliable, reproduceable mounting results for USB drives
Hi,
to address your question on how to ensure that your USB drive is mounted where/how you want it, you just need to add an fstab entry by UUID.
You can find the UUID of your device by mounting it manually or checking mtab to get the device path, then using
sudo vol_id --uuid /dev/deviceidofyourdrive
to obtain the UUID. Then, your fstab entry will look something like:
UUID=ff3fdxxx-bdxx-4xx3-85e1-87xxxxxxx382 /media/backup ext3 rw,relatime,user,uid=xxx,gid=xxx
Thus, no matter what other drives you may have plugged in to your system in what order, you can reliably mount the same drive to the same path. Maybe a little OT, but related and I thought it was useful.
@sixteenkats: Well, that proves you are not using any samba on your system. With you as root, the system couldn't find one of the main daemons for samba.
@davejay1970: Excellent post! Great advice!
A small problem on my end, though... vol_id is no longer in Gentoo and has been replaced by blkid. Now, not having seen the behavior from vol_id, I'm not sure how it formatted the output, so here is the output from a blkid query:
The listed "serial" above is the UUID of the attached device/filesystem. With lshw, you can also verify that what you are looking at *is* exactly what you want as you can check how large it is and where it is mounted while getting the UUID.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.