Bug 655892
Summary: | [vdsm] [storage] master domain mount point appears twice on SPM | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Haim <hateya> | ||||
Component: | vdsm | Assignee: | Eduardo Warszawski <ewarszaw> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | yeylon <yeylon> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 6.1 | CC: | danken, hateya, iheim, mgoldboi, Rhev-m-bugs, srevivo, yeylon, ykaul | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-11-30 17:36:15 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
The error line is usual and a result of the tune2fs parameters. -j is used for create the journal in case that it not exists (ext2). In case that a journal is present there is no harm. ffedbbc4-35f9-4235-8cf4-0bb747a6adf8::DEBUG::2010-11-21 09:55:09,008::misc::105::Storage.Misc.excCmd::(execCmd) '/usr/bin/sudo -n /sbin/tune2fs -j /dev/689bf013-d895-48d7-a314-12d35f43e176/master' (cwd None) ffedbbc4-35f9-4235-8cf4-0bb747a6adf8::DEBUG::2010-11-21 09:55:09,033::misc::125::Storage.Misc.excCmd::(execCmd) FAILED: <err> = 'The filesystem already has a journal.\n'; <rc> = 1 mount issue can't be reproduced. |
Created attachment 462066 [details] vdsm log. Description of problem: this is a very odd issues. i will start by printing mount table: [root@magenta-vdsd ~]# mount /dev/mapper/vg0-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") /dev/sda1 on /boot type ext4 (rw) /dev/mapper/vg0-lv_home on /home type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/mapper/689bf013--d895--48d7--a314--12d35f43e176-master on /rhev/data-center/mnt/blockSD/689bf013-d895-48d7-a314-12d35f43e176/master type ext3 (rw) qanashead.qa.lab.tlv.redhat.com:/export/hateya/rhel6.nfs-iso on /rhev/data-center/mnt/qanashead.qa.lab.tlv.redhat.com:_export_hateya_rhel6.nfs-iso type nfs (rw,soft,timeo=600,retrans=2,nosharecache,vers=3,addr=10.35.64.28) /dev/mapper/689bf013--d895--48d7--a314--12d35f43e176-master on /rhev/data-center/mnt/blockSD/689bf013-d895-48d7-a314-12d35f43e176/master type ext3 (rw) /dev/mapper/689bf013--d895--48d7--a314--12d35f43e176-master on /rhev/data-center/mnt/blockSD/689bf013-d895-48d7-a314-12d35f43e176/master type ext3 (rw) [root@magenta-vdsd ~]# it appears that in some point in time (vdsm.log.8.gz) in start spm task, vdsm decided to mount master storage domain mount point twice (i think, not sure) ffedbbc4-35f9-4235-8cf4-0bb747a6adf8::DEBUG::2010-11-21 09:55:09,033::misc::125::Storage.Misc.excCmd::(execCmd) FAILED: <err> = 'The filesystem already has a j ournal.\n'; <rc> = 1 ffedbbc4-35f9-4235-8cf4-0bb747a6adf8::DEBUG::2010-11-21 09:55:09,035::misc::105::Storage.Misc.excCmd::(execCmd) '/usr/bin/sudo -n /bin/mount /dev/689bf013-d895-48d7-a314-12d35f43e176/master /rhev/data-center/mnt/blockSD/689bf013-d895-48d7-a314-12d35f43e176/master' (cwd None) ffedbbc4-35f9-4235-8cf4-0bb747a6adf8::DEBUG::2010-11-21 09:55:09,227::misc::125::Storage.Misc.excCmd::(execCmd) SUCCESS: <err> = ''; <rc> = 0 ffedbbc4-35f9-4235-8cf4-0bb747a6adf8::DEBUG::2010-11-21 09:55:09,229::misc::105::Storage.Misc.excCmd::(execCmd) '/usr/bin/sudo -n /bin/chown vdsm:kvm /rhev/data-center/mnt/blockSD/689bf013-d895-48d7-a314-12d35f43e176/master' (cwd None) not sure for repro steps - see attached vdsm log.