Summary: | media-video/vidcutter-6.0.5.1 fails to emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Smith <chris> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chris Smith
2022-01-09 21:41:10 UTC
This doesn't look specific to vidcutter. ``` myhash, mysize = hashfunc_map[hashname].checksum_file(myfilename) File "/usr/lib/python3.9/site-packages/portage/checksum.py", line 95, in checksum_file data = f.read(blocksize) OSError: [Errno 5] Input/output error Terminated ``` Something weird about your PORTAGE_TMPDIR? Any I/O errors in dmesg? (In reply to Sam James from comment #1) > This doesn't look specific to vidcutter. > > ``` > myhash, mysize = hashfunc_map[hashname].checksum_file(myfilename) > File "/usr/lib/python3.9/site-packages/portage/checksum.py", line 95, in > checksum_file > data = f.read(blocksize) > OSError: [Errno 5] Input/output error > Terminated > ``` > > Something weird about your PORTAGE_TMPDIR? Any I/O errors in dmesg? Something weird, I've emerge a bunch of updates but when I try vidcutter I do get these: [ 92.123898] blk_update_request: critical medium error, dev nvme0n1, sector 1084616800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 92.271016] blk_update_request: critical medium error, dev nvme0n1, sector 1084616800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 There is no PORTAGE_TMPDIR defined in my environment. (In reply to Chris Smith from comment #2) > (In reply to Sam James from comment #1) > > This doesn't look specific to vidcutter. > > > > ``` > > myhash, mysize = hashfunc_map[hashname].checksum_file(myfilename) > > File "/usr/lib/python3.9/site-packages/portage/checksum.py", line 95, in > > checksum_file > > data = f.read(blocksize) > > OSError: [Errno 5] Input/output error > > Terminated > > ``` > > > > Something weird about your PORTAGE_TMPDIR? Any I/O errors in dmesg? > > Something weird, I've emerge a bunch of updates but when I try vidcutter I > do get these: > [ 92.123898] blk_update_request: critical medium error, dev nvme0n1, > sector 1084616800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 > [ 92.271016] blk_update_request: critical medium error, dev nvme0n1, > sector 1084616800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 > I think your SSD is failing and the distfile is on a bad part of the disk. > There is no PORTAGE_TMPDIR defined in my environment. That's fine, just sometimes people set it to something special / mount a tmpfs there. (In reply to Sam James from comment #3) > (In reply to Chris Smith from comment #2) > > (In reply to Sam James from comment #1) > > > This doesn't look specific to vidcutter. > > > > > > ``` > > > myhash, mysize = hashfunc_map[hashname].checksum_file(myfilename) > > > File "/usr/lib/python3.9/site-packages/portage/checksum.py", line 95, in > > > checksum_file > > > data = f.read(blocksize) > > > OSError: [Errno 5] Input/output error > > > Terminated > > > ``` > > > > > > Something weird about your PORTAGE_TMPDIR? Any I/O errors in dmesg? > > > > Something weird, I've emerge a bunch of updates but when I try vidcutter I > > do get these: > > [ 92.123898] blk_update_request: critical medium error, dev nvme0n1, > > sector 1084616800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 > > [ 92.271016] blk_update_request: critical medium error, dev nvme0n1, > > sector 1084616800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 > > > > I think your SSD is failing and the distfile is on a bad part of the disk. > > > There is no PORTAGE_TMPDIR defined in my environment. > > That's fine, just sometimes people set it to something special / mount a > tmpfs there. Yes, porttmpfs on /var/tmp/portage type tmpfs It's looking like you're right, jeez, brand new system this summer. closing, because it seems to be no problem with the package |