Hey everyone, hope all is well and keeping safe.

I tried searching for this online but do not know how to word it correctly to get an answer so sorry if this has been asked already.

I have a pc with two hard drives. The first one has the Slackware 14.1 software on it. The second one, is a 1TB hard drive, one partition, ext3, and has a share folder on it.

For some reason the share folder size is limited to 400GB. It does not use the entire 1TB hard drive. When viewing Properties of the shared folder, it would for example say 363GB used, 33GB free, 91% full.

When you copy files to that folder, at some stage, it will say there is not enough space. You then have to remove files from the folder to "free up more space" before you can copy to it again.

What do I have to change or do so that the share folder uses the entire drive and not just a portion of it?

Thanks in advance.

Welcome to LQ!

It would help to know more about your setup.
Please post the output of 'parted -l' run in a terminal as root.

It also would help to know how you are sharing the drive (both software and network) as well as the client side accessing the shares since that is a factor as well.

For example, on my PC I run boinc doing processing for science. I have set up to allow boinc to use up to 12 GB of space on a drive that has over 120GB free. Yet boinc only reports 30GB free.

Your space limitation could be due to the client and not the PC containing the drive itself.

Hi everyone, sorry for the late reply.

The details of parted -l:

Model: ATA ST1000DM010-2EP1 (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags

Number Start End Size Type File system Flags
1 32.3kB 1000GB 1000GB primary ext3


The client PCs used, to connect to the shared folder, is using Windows 7 / 10. We use the normal 'Map Network Drive' option to connect to the folder by giving it a Drive letter and filling in the Folder path. There is no quotas set up on any of the client PCs.

I am assuming it is setup somewhere in a config file. On the SlackWare 14.1 PC we have a gui installed as well but that is of no use. None of the configurations is viewable on there almost as if it is not set up yet. I am unfortunately not sure how that share folder was set up in the first place.

Thanks for the information. It confirms that the full 1000GB should be available.

It appears that the PC has been set up as a Samba server with Slackware 14.1 as the operating system. You can confirm this by running the command 'ps -ax | grep smbd' in a terminal. Any lines containing anything apart from "grep smbd" are running Samba processes.

I suggest checking the file system on the drive.
1. Become root in a terminal.
2. Confirm that there is an entry for the disk in /etc/fstab by running 'grep sdc1 /etc/fstab'.
3. Stop Samba by running 'sh /etc/rc.d/rc.samba stop'.
4. Unmount the drive by running 'umount /dev/sdc1'.
5. Check the file system by running 'e2fsck -p /dev/sdc1'. (See 'man e2fsck' for details.)

To restart Samba
6. Mount the drive by running 'mount /dev/sdc1'.
7. Restart Samba by running 'sh /etc/rc.d/rc.samba start'.

Hi again,

When I enter into a terminal the command: 'ps -ax | grep smbd' I get the following:

Warning a bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html (this site only brings up a 404 error)

809 ? Ss 0:25 /usr/sbin/smbd -D
821 ? S 0:03 /usr/sbin/smbd -D
2079 ? S 0:00 /usr/sbin/smbd -D
11776 ? S 0:00 /usr/sbin/smbd -D
13062 pts/1 S+ 0:00 grep smbd
15999 ? S 0:05 /usr/sbin/smbd -D

I read somewhere 'bad ps syntax' is just because I should have used 'ps u', so doing that gives me:

root 13066 0.0 0.0 7112 972 pts/1 S+ 12:31 0:00 grep smbd

And I have absolutely no idea what any of those things mean :-)

Also, I tried the second command namely 'grep sdc1 /etc/fstab' to see if there is an entry for the disk in fstab, but that displays nothing. It just returns to the prompt so I can type in the next command.

So I had a look at fstab by typing 'cat /etc/fstab' and get the following:

/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 1 1
/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x -gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0

At least I can say that the disk does not appear to be in that file. Most of it is sorta understandable except the bottom 3 entries. I have obviously only followed your instructions to point 2 mainly because I did not get any info after that command and wasn't sure if I should go ahead or if there is something else I should try?

I tried reading about the harddrive not being in the fstab file and people on the Internet were saying that some distributions of linux doesn't make use of fstab anymore but it started getting a bit confusing and the commands and files they talked about (mostly related to Ubuntu), I couldn't find on Slackware.

Can you make head or tail of the above? What would you suggest I do next? Thanks

The disk in question is definitely not listed in /etc/fstab. You can try
and
to see if it's mounted.

Hi shruggy, and thanks for commenting,

df -hT gives me:

/dev/sda3 ...
tmpfs ...
/dev/sdb1 ...
/dev/sdc1 ext3 367G 316G 34G 91% /media/very_long_assuming_unique_id

The first three entries, information on those looks correct. As you can see sdc1 is only using, or somehow been configured?, to use only 367G of the entire 1TB hard drive. I need to change that somehow so that it uses all of the space on the 1TB harddrive and not just 367G.


mount -lt ext2,ext3,ext4 gives me:

/dev/sda3 ...
/dev/sdc1 on /media/very_long_assuming_unique_id type ext3 (rw,nosuid,nodev,uhelper=udisks)

Disable samba and use udisksctl
test the size. The /etc/fstab needs to be hand edited - to put inside command to mount /dev/sdc1. But for me choice of ext3 for this size of disk is questionable. As I remember it just plain old ext2 plus journal. I would ask people here for suggestions what file system to chose.

The output of 'parted -L' shows only one disk /dev/sdc with one ext3 partition of 1000GB. The mountpoint for /dev/sdc1 on /media/very_long_assuming_unique_id reported from 'mount -lt' seems bogus.
The output of 'cat /etc/fstab' suggests a disk /dev/sda with multiple partitions, including a ext4 partition /dev/sda3 mounted on / (this is the Slackware 14.1 install)
The output of 'df -hT' shows an additional disk /dev/sdb, yet the OP reports only the presence of two hard drives.

Perhaps the output of 'cat /etc/mtab' would help.

Well, the output of mount was limited by -t to partitions of type ext[234]. I presume sdb1 is of different type, probably FAT32 or NTFS.

I am suspecting we are dealing with a running system that the OP is reluctant to touch without surety.
My guess is that an incorrect mount command command has been entered since the system was booted.
In Slackware, by default, mount commands can only be used by a user with root privileges. There may be clues in log files.

What about
to clarify.

I normally use "ps aux". I suspect that reading the man page for ps might give some enlightenment, such as

Can you post the complete output of the mount command and df -h (lsblk -f works as well)? I'm guessing that the shared folder has something mounted over it, thus limiting you to the free space of the partition that's on top.