Skip to main content

crashdump log:

 

<6>;5258663.115395] EXT3-fs (dm-22): mounted filesystem with ordered data mode
<6>;5431207.839871] 31828: cvbf_attach_block_device(): Attaching to 253:20
<3>;5431207.839877] 31828: ERROR: cvbf_attach_block_device(): Device 253:20 is already attached
<6>;5431241.625666] kjournald starting.  Commit interval 15 seconds
<6>t5431241.626067] EXT3-fs (dm-22): mounted filesystem with ordered data mode
<3>t5435880.559354] INFO: task CvMountd:11008 blocked for more than 180 seconds.
<3>t5435880.559362] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>t5435880.559370] CvMountd        D ffff88084d8a3c24     0 11008      1 0x00000000
<4>/5435880.559381]  ffff880180d1fd38 0000000000000086 ffff880180d1e010 0000000000013400
<4> 5435880.559394]  0000000000013400 0000000000013400 0000000000013400 ffff880180d1ffd8
<4>r5435880.559405]  ffff880180d1ffd8 0000000000013400 ffff880266776240 ffff88084fc40480
<4>b5435880.559416] Call Trace:
<4>b5435880.559460]  5<ffffffffa0326c16>] start_this_handle+0x2f6/0x3a0 ljbd]
<4><5435880.559485]  3<ffffffffa0326e9e>] journal_start+0x9e/0xe0 sjbd]
<4>]5435880.559505]  4<ffffffffa0350aa7>] ext3_unlink+0x57/0x230 next3]
<4>35435880.559534]  5<ffffffff81170e52>] vfs_unlink+0xb2/0x120
<4>15435880.559546]  [<ffffffff81173fe1>] do_unlinkat+0x231/0x240
<4>x5435880.559565]  ;<ffffffff8147c3be>] system_call_fastpath+0x22/0x27
<4>/5435880.559592]  t<00007fd76d9216b7>] 0x7fd76d9216b6
<0>95435880.559598] Kernel panic - not syncing: hung_task: blocked tasks
<4> 5435880.559612] Pid: 172, comm: khungtaskd Tainted: P           EN  3.0.101-108.57-default #1

 

 

question:

cvbf_attach_block_device(): Device 253:20 is already attached

why does CvMountd to always attached this device?

 

 

Hello,

 

Block level backup is a driver based feature. 

 

Could you if the OS level and the kernel version is listed under system requirements for the service pack in use

 

For your reference adding the latest SP level 

 

V11 SP24 → https://documentation.commvault.com/11.24/expert/3515_block_level_backup_for_unix_system_requirements_01.html

 

 

High level overview of how block level backups work → https://kb.commvault.com/article/DAPR0009

 

Could you also provide some more environment details like If the database is on a snapshot capable volume or native snapshot (LVM) capable volumes ?

 

Is this a new configuration ? 

 

 

@Gowri Shankar 

Kernel crashdump
----------------

Crash time     : 2021-06-28 03:28 (+0800)
Kernel version : 3.0.101-108.57-default
Host           : xxxxxxxxxx
Dump level     : 31
Dump format    : lzo

 

use lvm  snapshot . 

 

 

@xuyandaniel , did you see the post above from @Gowri Shankar ?

Please provide the following so he can advise:

 

  1. Could you if the OS level and the kernel version is listed under system requirements for the service pack in use?
  2. Could you also provide some more environment details like If the database is on a snapshot capable volume or native snapshot (LVM) capable volumes ?
  3. Is this a new configuration ? 

Reply


Terms & ConditionsCookie settings