LinuxQuestions.org - Automount Drive

- Fedora (https://www.linuxquestions.org/questions/fedora-35/)

- - Automount Drive (https://www.linuxquestions.org/questions/fedora-35/automount-drive-819787/)

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

Code:

$ tar --version

tar (GNU tar) 1.22

Code:

$ uname -r

2.6.32.9-67.fc12.x86_64

Code:

$ samba --version

bash: samba: command not found

Please see http://www.linuxquestions.org/questi...r-limit-627582 for reference - this has been split out from a debian thread.

Try the following:

Code:

~ # smbd -V

and let us know what comes back from that.

HTH. Let us know.

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.

Quote:

Originally Posted by ShadowCat8 (Post 4033008)

Try the following:

Code:

~ # smbd -V

and let us know what comes back from that.

HTH. Let us know.

Code:

# smbd -V

bash: smbd: command not found

Michaelk - I thought it was NTFS, but I just checked and I was wrong. I will reformat and see if that is the problem.

I assumed you desire windows compatibility but you could always format as ext3 etc.

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.

cheers

Greetings,

@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:

Code:

~ # blkid -p -u filesystem,other /dev/sdb1

/dev/sdb1: UUID="acb5cc75-31dd-4629-8f4e-81b6d4433f5e" VERSION="1.0" TYPE="ext3" USAGE="filesystem" 

~ #

And, an easier way (IMHO) to get that info for what is connected to your system is using lshw:

Code:

                *-disk

                      description: SCSI Disk

                      product: STORAGE DEVICE

                      vendor: Generic

                      physical id: 0.0.0

                      bus info: scsi@7:0.0.0

                      logical name: /dev/sdb

                      version: 9328

                      size: 244MiB (256MB)

                      capabilities: removable

                    *-medium

                        physical id: 0

                        logical name: /dev/sdb

                        size: 244MiB (256MB)

                        capabilities: partitioned partitioned:dos

                        configuration: signature=3e146322

                      *-volume

                            description: EXT3 volume

                            vendor: Linux

                            physical id: 1

                            logical name: /dev/sdb1

                            logical name: /mnt/usb-dev

                            version: 1.0

                            serial: acb5cc75-31dd-4629-8f4e-81b6d4433f5e

                            size: 244MiB

                            capacity: 244MiB

                            capabilities: primary journaled extended_attributes large_files huge_files recover ext3 ext2 initialized

                            configuration: created=2006-03-23 11:38:40 filesystem=ext3 modified=2010-07-16 11:47:19 mount.fstype=ext3 mount.options=rw,errors=continue,data=ordered mounted=2010-07-16 11:47:19 state=mounted

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.

Just my 2¢.