** Changed in: open-iscsi (Ubuntu)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is seen during
Hi Jitendra! No problem at all, let's keep it open for the time you need.
Let me know in case you have any news.
Cheers,
Guilherme
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided =>
Hi Guilherme,
We have started doing focused long-run, performance, stress testing on multiple
setups. This is expected to take more than a month time.
So based on the internal discussion, we request to keep this bug open until
July end.
Please let me know if you have any concerns.
Regards
Sure Jitendra, all fine by me!! Take your time - if you manage to reproduce,
let me know.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is
Hi Guilherme,
I am doing good. Thank you.
About the bug, I am still trying to reproduce it. Because of some other issues
I could not get to the number of test cycles after which this bug reproduce.
Now, I am working on two different setups to reproduce this. I suggest to wait
until mid next
Hi Jitendra, how are you doing? Is there any news on this bug? If you cannot
reproduce it anymore, we could mark it as "Invalid" - and "re-open" in case it
reproduces again.
Cheers!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Cool, that's indeed good news Jitendra. Thanks for the heads-up.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is seen during SCSI
Hi Guilherme,
Quick update on this, test is still running and haven't seen kernel panic so
far.
I will keep it running for few more days.
Regards
Jitendra
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Perfect, thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is seen during SCSI remove_device.
To manage notifications about this bug go to:
Hi Guilherme,
I have configured kdump, enabled "/proc/sys/kernel/hung_task_panic" and started
the test.
Observed couple of test failures but those are unrelated.
Will keep monitoring setup and update you as soon as I hit repro.
Jitendra
--
You received this bug notification because you are a
Hi Jitendra, thanks for the effort! Let me know your issues with kdump, hope I
can help.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is
Thanks Guilherme for the details to setup KDUMP.
I tried these steps on Ubuntu VM (just to ensure I don't mess up with physical
setup) and but landed into some issues.
I am still working on to configure KDUMP and repro the issue.
Will keep you posted as things progress.
Regards
Jitendra
--
You
Hi Jitendra, I am sorry for the delay - I've tried to reproduce both using
regular SCSI device in a virtual machine and by using iSCSI, and neither was a
successful reproducer. Based on the stack traces I see in your "echo w" output,
it seems to be related with your special iSCSI target.
Also,
Thank you so much for the update, Guilherme.
I can surely try to reproduce issue again to collect kdump, Please share
the configuration setting for kdump.
One question,
Is there anything more that can be captured from the current repro setup? If
not, then I will repurpose the same setup.
Hi Jitendra, my sincere apologies for the delay, I'm still trying to reproduce
this.
I hope to have more meaningful updates for you until the end of this week.
Meanwhile, let me ask you something: would you be wiling to collect a
kdump if the issue reproduces again? That'd be a helpful tool to
Hi Guilherme,
Sorry to bother you again.
Just thought of checking with you if you have any update on below,
1. Are you able to repro issue at your end?
2. Were you able to confirm if its a lock issue?
Thanks
Jitendra
--
You received this bug notification because you are a member of Ubuntu
Thank you Guilherme for the response and taking time to look at this.
Thought of checking with you,
if there is any further update on reproducing issue at your end? or
need more information from the repro setup that I have?
Regards
Jitendra
--
You received this bug notification because you
Thanks for the clarification Jitendra, and for correcting my command! It
was indeed wrong, apologies - the correct file to write is the one
you've used, "/proc/sysrq-trigger".
So, it seems we have a lock "situation" in iSCSI/scsi, I'll need to study more
the code to understand how that is
** Attachment added: "Output of dmesg > /root/dmesg.l"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1914456/+attachment/5472103/+files/dmesg.l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Output of dmesg -c > /root/dmesg.out"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1914456/+attachment/5472100/+files/dmesg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Following command failed
root# echo w > /proc/sysrq
bash: /proc/sysrq: No such file or directory
So tried below command and it worked,
root# echo w > /proc/sysrq-trigger
** Attachment added: "Output of dmesg > /root/dmesg.w"
Hey Guilherme,
Please find below response,
(#a) We are using Cisco Hyperflex iSCSI storage. Following link has more
details about it.
https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/AdminGuide/4-5/b-hxdp-admin-guide-4-5/m-hxdp-iscsi-manage.html
Hi Jitendra, thanks for the data you provided. I have some questions in
order I can better simulate your environment:
(a) You said "vendor's iSCSI target" <- can you elaborate more about
this, like which vendor/solution are we talking about?
(b) You mention, in the last comment: "note that
Hi Guilherme,
Please find attachment containing output of commands,
"dmesg", "lspci -vvv", "lsblk", "ls -l /sys/block", "mount".
Also please note that Ubuntu host is running in a virtualized
environment.
** Attachment added: "cmd_output.txt"
Hi Jitendra, thanks for the heads-up. Can you collect the output of the
following commands, in the machines's current state ? (no need to
reproduce for that)
"dmesg", "lspci -vvv", "lsblk", "ls -l /sys/block", "mount"
That'd help a lot to determine what is your hardware and maybe help me to
Hi Guilherme,
Here is the update from my side.
1. sosreport command hung at below message,
Setting up archive ...
Setting up plugins ...
Running plugins. Please wait ...
Finishing plugins [Running: block btrfs]
Hi Jitendra, thanks for your prompt response. I'd like to ask you the
following data in order to speed-up the debug process:
1) Right before the test, please collect the outputs of: "dmesg", "lspci
-vvv", "lsblk", "ls -l /sys/block", "mount"
2) After the I/O test + SCSI removal, collect please a
Hi Guilherme,
There is some confidential data present in sosreport and it is scattered all
over the place. So team is evaluating if .xz file can be sanitize.
Meanwhile, Can you please let me know, specific information that I can
extract from the system to share with you?
--
You received this
Thanks for the response Guilherme.
I will work with my team to see if there is anything specific that needs to be
filter out. Will provide you an update soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jitendra, thanks for your report! Could you collect a sosreport for us, in
order we can have more information (even to try reproducing the issue in-house)?
For that, please execute the following commands as root user:
apt-get install sosreport
sosreport
A "sosreport-X.tar.xz" file will
Just for reference,
Following command is used to delete SCSI device.
echo "1" >> /sys/block//device/delete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is
** Description changed:
Ubuntu Release
--
#lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
#cat /proc/version_signature
Ubuntu 4.15.0-122.124-generic 4.15.18
Package version
---
#apt-cache policy open-iscsi
open-iscsi:
-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: open-iscsi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
33 matches
Mail list logo