From: Jun Wang junw99@yahoo.com
With some corrupted vmcore files, the vmcore-dmesg.txt file may grow forever till the kdump disk becomes full, and also probably causes the disk error messages as follow: ... sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00 blk_update_request: I/O error, dev sda, sector 134630552 sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00 blk_update_request: I/O error, dev sda, sector 134630552 ...
Lets limit the size of vmcore-dmesg.txt to avoid such problems.
Signed-off-by: Jun Wang junw99@yahoo.com Signed-off-by: Lianbo Jiang lijiang@redhat.com --- dracut-kdump.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dracut-kdump.sh b/dracut-kdump.sh index 2ae1c7c5d70d..ce56459ed088 100755 --- a/dracut-kdump.sh +++ b/dracut-kdump.sh @@ -102,8 +102,8 @@ save_vmcore_dmesg_ssh() { local _opts="$3" local _location=$4
- echo "kdump: saving vmcore-dmesg.txt" - $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt" + echo "kdump: saving vmcore-dmesg.txt, up to 100MB" + $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt bs=512 count=204800" _exitcode=$?
if [ $_exitcode -eq 0 ]; then
On 08/02/19 at 09:29pm, Lianbo Jiang wrote:
From: Jun Wang junw99@yahoo.com
With some corrupted vmcore files, the vmcore-dmesg.txt file may grow forever till the kdump disk becomes full, and also probably causes the disk error messages as follow: ... sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00 blk_update_request: I/O error, dev sda, sector 134630552 sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00 blk_update_request: I/O error, dev sda, sector 134630552 ...
Lets limit the size of vmcore-dmesg.txt to avoid such problems.
Signed-off-by: Jun Wang junw99@yahoo.com Signed-off-by: Lianbo Jiang lijiang@redhat.com
dracut-kdump.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dracut-kdump.sh b/dracut-kdump.sh index 2ae1c7c5d70d..ce56459ed088 100755 --- a/dracut-kdump.sh +++ b/dracut-kdump.sh @@ -102,8 +102,8 @@ save_vmcore_dmesg_ssh() { local _opts="$3" local _location=$4
- echo "kdump: saving vmcore-dmesg.txt"
- $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt"
- echo "kdump: saving vmcore-dmesg.txt, up to 100MB"
- $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt bs=512 count=204800" _exitcode=$?
Why only fix ssh path?
if [ $_exitcode -eq 0 ]; then-- 2.17.1
We use netdump with ssh target only. In additoon, unlike local disk kdump, the negative impact of filling up disks on centralized kdump server goes way beyond the kdump client host itself.
Other path should also be fixed, sooner or later, depending on severity of the impact.
Thanks,
Jun
Sent from Yahoo Mail for iPhone
On Monday, August 5, 2019, 8:05 PM, Dave Young dyoung@redhat.com wrote:
On 08/02/19 at 09:29pm, Lianbo Jiang wrote:
From: Jun Wang junw99@yahoo.com
With some corrupted vmcore files, the vmcore-dmesg.txt file may grow forever till the kdump disk becomes full, and also probably causes the disk error messages as follow: ... sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00 blk_update_request: I/O error, dev sda, sector 134630552 sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00 blk_update_request: I/O error, dev sda, sector 134630552 ...
Lets limit the size of vmcore-dmesg.txt to avoid such problems.
Signed-off-by: Jun Wang junw99@yahoo.com Signed-off-by: Lianbo Jiang lijiang@redhat.com
dracut-kdump.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dracut-kdump.sh b/dracut-kdump.sh index 2ae1c7c5d70d..ce56459ed088 100755 --- a/dracut-kdump.sh +++ b/dracut-kdump.sh @@ -102,8 +102,8 @@ save_vmcore_dmesg_ssh() { local _opts="$3" local _location=$4 - echo "kdump: saving vmcore-dmesg.txt" - $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt" + echo "kdump: saving vmcore-dmesg.txt, up to 100MB" + $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt bs=512 count=204800" _exitcode=$?
Why only fix ssh path?
if [ $_exitcode -eq 0 ]; then -- 2.17.1
在 2019年08月06日 11:21, Jun Wang 写道:
We use netdump with ssh target only. In additoon, unlike local disk kdump, the negative impact of filling up disks on centralized kdump server goes way beyond the kdump client host itself.
Other path should also be fixed, sooner or later, depending on severity of the impact.
This patch should be improved this time, and also fix other path, not only ssh path.
I will post v2 later.
Thanks.
Thanks,
Jun
Sent from Yahoo Mail for iPhone https://overview.mail.yahoo.com/?.src=iOS
On Monday, August 5, 2019, 8:05 PM, Dave Young dyoung@redhat.com wrote:
On 08/02/19 at 09:29pm, Lianbo Jiang wrote: > From: Jun Wang <junw99@yahoo.com <mailto:junw99@yahoo.com>> > > With some corrupted vmcore files, the vmcore-dmesg.txt file may grow > forever till the kdump disk becomes full, and also probably causes > the disk error messages as follow: > ... > sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 08 06 <tel:28%2000%2008%2006> 4c 98 00 00 08 00 <tel:98%2000%2000%2008%2000> > blk_update_request: I/O error, dev sda, sector 134630552 <tel:134630552> > sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 08 06 <tel:28%2000%2008%2006> 4c 98 00 00 08 00 <tel:98%2000%2000%2008%2000> > blk_update_request: I/O error, dev sda, sector 134630552 <tel:134630552> > ... > > Lets limit the size of vmcore-dmesg.txt to avoid such problems. > > Signed-off-by: Jun Wang <junw99@yahoo.com <mailto:junw99@yahoo.com>> > Signed-off-by: Lianbo Jiang <lijiang@redhat.com <mailto:lijiang@redhat.com>> > --- > dracut-kdump.sh | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/dracut-kdump.sh b/dracut-kdump.sh > index 2ae1c7c5d70d..ce56459ed088 100755 > --- a/dracut-kdump.sh > +++ b/dracut-kdump.sh > @@ -102,8 +102,8 @@ save_vmcore_dmesg_ssh() { > local _opts="$3" > local _location=$4 > > - echo "kdump: saving vmcore-dmesg.txt" > - $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt" > + echo "kdump: saving vmcore-dmesg.txt, up to 100MB" > + $_dmesg_collector /proc/vmcore | ssh $_opts $_location "dd of=$_path/vmcore-dmesg-incomplete.txt bs=512 count=204800" > _exitcode=$? Why only fix ssh path? > > if [ $_exitcode -eq 0 ]; then > -- > 2.17.1 >