Description of problem: I get this type of I/O error always when i update my kernel in text environment on fedora 7 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 This has been happening with the latest kernel and with earlier ones for long as i have been updating my system through text interface with smart and have been doing that long. Haven't noticed that this would be causing any problems that would cause my system not to work, but have been getting this so long that thought to report this.
Created attachment 153438 [details] strace of grubby run installing kernel Looks like it scans /sys/block, finds fd0 and tries to open it for some reason. In fact, it seems to try twice. Hangs for about 4 minutes on floppyless systems. Particularly annoying during install. Related bug 155876
Culprit seems to be this: dev = nashGetPathBySpec(_nash_context, dev);
Why doesn't block_find_fs_by_keyvalue make use of the cache in nashContext *nc to find the label, ala blkid_get_devname() in libblkid?
Just wondering, but is this going to be fixed someday?
tjustt - are you just giving up on this? I'd like to see this fixed someday. Causes rather annoying timeouts and seems relatively straightforward to fix.
I would want this to be fixed too, but this has been here about from test 2 and pretty much nothing has happened! I'm not sure but it could even be that this is the problem thats making my files get corrupted when moving them through USB.