| View previous topic :: View next topic |
| Author |
Message |
dark-wulf
n00b
Joined: 02 Feb 2006
Posts: 40
|
 Posted: Thu Jan 11, 2018 10:56 am Post subject: OSError: [Errno 117] Structure needs cleaning |
 |
|
I am just upgrading to profile 17.0 and portage failed while emerge -e same happens for nvidia-drivers
| Code: |
running install_egg_info
Writing /media/temp/portage/temp/portage/sys-apps/portage-2.3.19-r1/image/_python3.4/usr/lib64/python3.4/site-packages/portage-2.3.19-py3.4.egg-info
* python3_4: running distutils-r1_run_phase python_install_all
ERROR:root:Failed to copy file: _parsed_options=Namespace(group=-1, mode=420, owner=-1), source=b'/media/temp/portage/temp/portage/sys-apps/portage-2.3.19-r1/files/portage-ccache.conf', dest_dir=b'/media/temp/portage/temp/portage/sys-apps/portage-2.3.19-r1/image//usr/lib/tmpfiles.d'
Traceback (most recent call last):
File "/media/temp/portage/temp/portage/._portage_reinstall_.6jvmolc5/bin/doins.py", line 184, in run
copyfile(source, dest)
File "/media/temp/portage/temp/portage/._portage_reinstall_.6jvmolc5/pym/portage/util/file_copy/__init__.py", line 30, in _optimized_copyfile
_file_copy(src_file.fileno(), dst_file.fileno())
OSError: [Errno 117] Structure needs cleaning
* ERROR: sys-apps/portage-2.3.19-r1::gentoo failed (install phase):
* doins failed
|
| Code: |
ERROR:root:Failed to copy file: _parsed_options=Namespace(group=-1, mode=420, owner=-1), source=b'/media/temp/portage/temp/portage/x11-drivers/nvidia-drivers-390.12/files/nvidia-rmmod.conf', dest_dir=b'/media/temp/portage/temp/portage/x11-drivers/nvidia-drivers-390.12/image//etc/modprobe.d'
Traceback (most recent call last):
File "/usr/lib/portage/python3.4/doins.py", line 184, in run
copyfile(source, dest)
File "/usr/lib64/python3.4/site-packages/portage/util/file_copy/__init__.py", line 30, in _optimized_copyfile
_file_copy(src_file.fileno(), dst_file.fileno())
OSError: [Errno 117] Structure needs cleaning
* ERROR: x11-drivers/nvidia-drivers-390.12::gentoo failed (install phase):
* doins failed
|
I have checked all drives (all ext4, root on ssd 94% health), deleted the files that cause it and did not touch any partition with some windows ext4 driver (this is what was what i have found that could cause it)
Thanks for any help 
_________________
Gentoo rulez!!!
Gentoo for every one!!!
Gentoo for president!!! |
|
| Back to top |
|
 |
blopsalot
Apprentice
Joined: 28 Jan 2017
Posts: 231
|
| Posted: Sun Jan 14, 2018 6:24 am Post subject: |
|
|
it's filesystem corruption and there are too many possible causes to even list. it is not unique to a windows ext4 driver. use debugfs.
edit: SMART info is not always reliable, I would consider possibility drive is dying. |
|
| Back to top |
|
|
dark-wulf
n00b
Joined: 02 Feb 2006
Posts: 40
|
| Posted: Fri Jan 19, 2018 1:28 pm Post subject: |
|
|
Thanks for the hint, had over seen this in messages
| Code: | kernel: EXT4-fs (sdf2): error count since last fsck: 4
kernel: EXT4-fs (sdf2): initial error at time 1515666089: ext4_map_blocks:581: inode 19917: block 1917853731
kernel: EXT4-fs (sdf2): last error at time 1515784639: ext4_map_blocks:581: inode 19917: block 1917853731
|
I think i will do a back up and reformat the drive on the other hand the ssd is 8 years old with 5 years uptime now, maybe time for a new on 
edit: And a new install with the 17.0 profile would be a good idea too  since it failed to compile somewhere at half
_________________
Gentoo rulez!!!
Gentoo for every one!!!
Gentoo for president!!! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
