1 |
thelma@×××××××××××.com wrote: |
2 |
> On 07/03/2020 03:12 PM, thelma@×××××××××××.com wrote: |
3 |
>> I have a USB flash drive with ext2 file system and when I try to copy a |
4 |
>> file I get an error "No space left on device" |
5 |
>> |
6 |
>> df -Th |
7 |
>> Filesystem Type Size Used Avail Use% Mounted on |
8 |
>> /dev/sdb1 ext2 944M 1.4M 943M 1% /run/media/thelma/UUI |
9 |
>> |
10 |
>> df -i |
11 |
>> Filesystem Inodes IUsed IFree IUse% Mounted on |
12 |
>> /dev/sdb1 61440 21 61419 1% /run/media/thelma/UUI |
13 |
>> |
14 |
> Here is more info: |
15 |
> |
16 |
> tune2fs -l /dev/sdb1 |
17 |
> tune2fs 1.43.6 (29-Aug-2017) |
18 |
> Filesystem volume name: UUI |
19 |
> Last mounted on: /run/media/thelma/UUI |
20 |
> Filesystem UUID: 4348ab9b-f3ec-4908-b11b-73a460882cd5 |
21 |
> Filesystem magic number: 0xEF53 |
22 |
> Filesystem revision #: 1 (dynamic) |
23 |
> Filesystem features: ext_attr resize_inode dir_index filetype |
24 |
> sparse_super large_file |
25 |
> Filesystem flags: signed_directory_hash |
26 |
> Default mount options: user_xattr acl |
27 |
> Filesystem state: not clean with errors |
28 |
> Errors behavior: Continue |
29 |
> Filesystem OS type: Linux |
30 |
> Inode count: 61440 |
31 |
> Block count: 245504 |
32 |
> Reserved block count: 0 |
33 |
> Free blocks: 241291 |
34 |
> Free inodes: 61419 |
35 |
> First block: 0 |
36 |
> Block size: 4096 |
37 |
> Fragment size: 4096 |
38 |
> Reserved GDT blocks: 59 |
39 |
> Blocks per group: 32768 |
40 |
> Fragments per group: 32768 |
41 |
> Inodes per group: 7680 |
42 |
> Inode blocks per group: 480 |
43 |
> Filesystem created: Wed Oct 7 08:28:52 2015 |
44 |
> Last mount time: Fri Jul 3 15:25:24 2020 |
45 |
> Last write time: Fri Jul 3 15:27:21 2020 |
46 |
> Mount count: 2594 |
47 |
> Maximum mount count: -1 |
48 |
> Last checked: Wed Oct 7 08:28:52 2015 |
49 |
> Check interval: 0 (<none>) |
50 |
> Lifetime writes: 61 MB |
51 |
> Reserved blocks uid: 0 (user root) |
52 |
> Reserved blocks gid: 0 (group root) |
53 |
> First inode: 11 |
54 |
> Inode size: 256 |
55 |
> Required extra isize: 28 |
56 |
> Desired extra isize: 28 |
57 |
> Default directory hash: half_md4 |
58 |
> Directory Hash Seed: dbea2a4c-9588-4364-a8de-96e68f24db09 |
59 |
> FS Error count: 126 |
60 |
> First error time: Sat Jun 6 19:33:04 2020 |
61 |
> First error function: mb_free_blocks |
62 |
> First error line #: 1470 |
63 |
> First error inode #: 13 |
64 |
> First error block #: 1589 |
65 |
> Last error time: Fri Jul 3 15:27:21 2020 |
66 |
> Last error function: __ext4_new_inode |
67 |
> Last error line #: 884 |
68 |
> Last error inode #: 0 |
69 |
> Last error block #: 0 |
70 |
> |
71 |
> |
72 |
|
73 |
|
74 |
I notice this little bit. |
75 |
|
76 |
|
77 |
Filesystem state: not clean with errors |
78 |
|
79 |
and |
80 |
|
81 |
FS Error count: 126 |
82 |
|
83 |
|
84 |
It may be that it was removed while still mounted. Maybe a file system |
85 |
check would help?? |
86 |
|
87 |
I did some googling. For the instances I found like this, people took |
88 |
all files off the USB device, re-partitioned and reformatted the device |
89 |
and then copied the files back. That seemed to be the cleanest and |
90 |
easiest solution. If checking the file system doesn't help, that may be |
91 |
your next option. I might add, some had to do that with new USB sticks |
92 |
straight out of the box. |
93 |
|
94 |
I also saw mentions of inodes but generally, that didn't turn out to be |
95 |
the problem. I think you can check those with df -i. |
96 |
|
97 |
Hope that helps or someone else comes along with a better idea. |
98 |
|
99 |
Dale |
100 |
|
101 |
:-) :-) |