On Tue, Feb 25, 2020 at 4:53 PM Samuel Sieb <[email protected]> wrote: > > On 2/25/20 2:17 AM, George R Goffe via test wrote: > > /dev/sda3 8390656 33556479 25165824 12G 82 Linux swap / > > Solaris > > > > that offset in the lseek seems like an awfully big number don't you think? > > The "blkid" command is going after /dev/sda3. > > > > 402 261523 openat(AT_FDCWD, "/dev/sda3", O_RDONLY|O_NONBLOCK|O_CLOEXEC) = 4 > > 403 261523 fadvise64(4, 0, 0, POSIX_FADV_RANDOM) = 0 > > 404 261523 fstat(4, {st_dev=makedev(0, 0x6), st_ino=2227, > > st_mode=S_IFBLK|0660, st_nlink=1, st_uid=0, st_gid=6, st_blksize=4096, > > st_blocks=0, st_rdev=makedev(0x8, 0x3), st_atime=15825368404 99 /* > > 2020-02-24T01:34:59.922441488-0800 */, st_atime_nsec=922441488, > > st_mtime=1582536864 /* 2020-02-24T01:34:24.860780764-0800 */, > > st_mtime_nsec=860780764, st_ctime=1582536864 /* 20404 > > 20-02-24T01:34:24.860780764-0800 */, st_ctime_nsec=860780764}) = 0 > > 405 261523 ioctl(4, BLKGETSIZE64, [12884901888]) = 0 > > 417 261523 lseek(4, 12884836352, SEEK_SET > > I assume this on the host system, not the VM. blkid is trying to seek > somewhere near the end of the swap partition and getting stuck. That is > a very strange call to get stuck on. Are there any messages in the > journal? Check the SMART status of your hard drive.
It probably can't get stuck on read() indefinitely because of the kernel command timer. Default is 30 seconds, then a link reset is issued which clears the entire command queue in the drive. But link resets are recorded in the journal. Or if not, it's some other reason and the journal will likely give some hint. -- Chris Murphy _______________________________________________ test mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
