thelma@sys-concept.com wrote:
> On 07/03/2020 03:12 PM, thelma@sys-concept.com wrote:
>> I have a USB flash drive with ext2 file system and when I try to copy a
>> file I get an error "No space left on device"
>>
>> df -Th
>> Filesystem     Type      Size  Used Avail Use% Mounted on
>> /dev/sdb1      ext2      944M  1.4M  943M   1% /run/media/thelma/UUI
>>
>> df -i
>> Filesystem       Inodes  IUsed    IFree IUse% Mounted on
>> /dev/sdb1         61440     21    61419    1% /run/media/thelma/UUI
>>
> Here is more info:
>
> tune2fs -l /dev/sdb1
> tune2fs 1.43.6 (29-Aug-2017)
> Filesystem volume name:   UUI
> Last mounted on:          /run/media/thelma/UUI
> Filesystem UUID:          4348ab9b-f3ec-4908-b11b-73a460882cd5
> Filesystem magic number:  0xEF53
> Filesystem revision #:    1 (dynamic)
> Filesystem features:      ext_attr resize_inode dir_index filetype
> sparse_super large_file
> Filesystem flags:         signed_directory_hash
> Default mount options:    user_xattr acl
> Filesystem state:         not clean with errors
> Errors behavior:          Continue
> Filesystem OS type:       Linux
> Inode count:              61440
> Block count:              245504
> Reserved block count:     0
> Free blocks:              241291
> Free inodes:              61419
> First block:              0
> Block size:               4096
> Fragment size:            4096
> Reserved GDT blocks:      59
> Blocks per group:         32768
> Fragments per group:      32768
> Inodes per group:         7680
> Inode blocks per group:   480
> Filesystem created:       Wed Oct  7 08:28:52 2015
> Last mount time:          Fri Jul  3 15:25:24 2020
> Last write time:          Fri Jul  3 15:27:21 2020
> Mount count:              2594
> Maximum mount count:      -1
> Last checked:             Wed Oct  7 08:28:52 2015
> Check interval:           0 (<none>)
> Lifetime writes:          61 MB
> Reserved blocks uid:      0 (user root)
> Reserved blocks gid:      0 (group root)
> First inode:              11
> Inode size:	          256
> Required extra isize:     28
> Desired extra isize:      28
> Default directory hash:   half_md4
> Directory Hash Seed:      dbea2a4c-9588-4364-a8de-96e68f24db09
> FS Error count:           126
> First error time:         Sat Jun  6 19:33:04 2020
> First error function:     mb_free_blocks
> First error line #:       1470
> First error inode #:      13
> First error block #:      1589
> Last error time:          Fri Jul  3 15:27:21 2020
> Last error function:      __ext4_new_inode
> Last error line #:        884
> Last error inode #:       0
> Last error block #:       0
>
>


I notice this little bit.


Filesystem state: not clean with errors

and

FS Error count:           126


It may be that it was removed while still mounted.  Maybe a file system
check would help??

I did some googling.  For the instances I found like this, people took
all files off the USB device, re-partitioned and reformatted the device
and then copied the files back.  That seemed to be the cleanest and
easiest solution.  If checking the file system doesn't help, that may be
your next option.  I might add, some had to do that with new USB sticks
straight out of the box.

I also saw mentions of inodes but generally, that didn't turn out to be
the problem.  I think you can check those with df -i. 

Hope that helps or someone else comes along with a better idea.

Dale

:-)  :-)