[Ocfs2-users] ocfs2_fill_super:616 ERROR

Fri Jun 1 11:52:31 PDT 2007

Ahh... you are running 1.2.3. We had addressed few umount issues
in 1.2.4 that could cause this. As in, the /debug entry is not
removed during umount as can be seen in your output.

This was fixed in 1.2.4.

Kendall, Kim wrote:
> I only see that UUID once. All the other UUIDs have been changed from
> their production counterparts: (UUID ending in 8550 is the beast giving
> the problem)
>
> After mounting debugfs:
> -----------------------
> # ls -R /debug
> /debug:
> ocfs2
>
> /debug/ocfs2:
> 016B8942717645D2BD94457A34D78550  59451007DF8249B6A933AAD1C8B66BCB
> AFC39875A3D441929EA5DE92CDE55A5C
> 0186F4535F0848EAB43C0EF622EE6FDA  5F1458E28D824328A13EFF9F006632C9
> DE8AED12C34145B3A7793CCB8A94FB89
> 355D669CD10049918234B6C2118F0367  6A70AE3D409E41B68F58415C2963192D
> 4A489F8B8E8240268BA59854F47B3457  7E088BF63307468C87E19CC2D48E07DD
>
> /debug/ocfs2/016B8942717645D2BD94457A34D78550:
>
> /debug/ocfs2/0186F4535F0848EAB43C0EF622EE6FDA:
> locking_state
>
> /debug/ocfs2/355D669CD10049918234B6C2118F0367:
> locking_state
>
> /debug/ocfs2/4A489F8B8E8240268BA59854F47B3457:
> locking_state
>
> /debug/ocfs2/59451007DF8249B6A933AAD1C8B66BCB:
> locking_state
>
> /debug/ocfs2/5F1458E28D824328A13EFF9F006632C9:
> locking_state
>
> /debug/ocfs2/6A70AE3D409E41B68F58415C2963192D:
> locking_state
>
> /debug/ocfs2/7E088BF63307468C87E19CC2D48E07DD:
> locking_state
>
> /debug/ocfs2/AFC39875A3D441929EA5DE92CDE55A5C:
> locking_state
>
> /debug/ocfs2/DE8AED12C34145B3A7793CCB8A94FB89:
> locking_state
>
> Also looked at the /proc/fs/ocfs2:
> ----------------------------------
> # cat */uuid
> 5F1458E28D824328A13EFF9F006632C9
> AFC39875A3D441929EA5DE92CDE55A5C
> 59451007DF8249B6A933AAD1C8B66BCB
> 0186F4535F0848EAB43C0EF622EE6FDA
> 7E088BF63307468C87E19CC2D48E07DD
> DE8AED12C34145B3A7793CCB8A94FB89
> 355D669CD10049918234B6C2118F0367
> 6A70AE3D409E41B68F58415C2963192D
> 4A489F8B8E8240268BA59854F47B3457
>
> But something strange about this volume (emcpowerl) from the rest:
> ------------------------------------------------------------------
> (note - /dev/sdb is the device emcpowerl is mapped to)
> # mounted.ocfs2 -f
> Device                FS     Nodes
> /dev/sdb              ocfs2  appsdb1util, 1, 2, 3
> /dev/sdc              ocfs2  Not mounted
> /dev/sdd              ocfs2  Not mounted
> /dev/sde              ocfs2  appsdb1util
> /dev/sdf              ocfs2  appsdb1util
> /dev/sdg              ocfs2  appsdb1util
> /dev/sdh              ocfs2  appsdb1util
> /dev/sdi              ocfs2  appsdb1util
> /dev/sdj              ocfs2  appsdb1util
> /dev/sdk              ocfs2  appsdb1util
> /dev/sdl              ocfs2  appsdb1util
> /dev/sdm              ocfs2  appsdb1util
> /dev/emcpowera        ocfs2  appsdb1util
> /dev/emcpowerb        ocfs2  appsdb1util
> /dev/emcpowerc        ocfs2  appsdb1util
> /dev/emcpowerd        ocfs2  appsdb1util
> /dev/emcpowere        ocfs2  appsdb1util
> /dev/emcpowerf        ocfs2  appsdb1util
> /dev/emcpowerg        ocfs2  appsdb1util
> /dev/emcpowerh        ocfs2  appsdb1util
> /dev/emcpoweri        ocfs2  appsdb1util
> /dev/emcpowerj        ocfs2  Not mounted
> /dev/emcpowerk        ocfs2  Not mounted
> /dev/emcpowerl        ocfs2  appsdb1util, 1, 2, 3  <---- This is the
> volume
>
>
> There are NO conflicting UUIDs!
> -------------------------------
> # mounted.ocfs2 -d
> Device                FS     UUID                                  Label
> /dev/sdb              ocfs2  016b8942-7176-45d2-bd94-457a34d78550  dbf1
> /dev/sdc              ocfs2  8ddded83-6871-4fff-961e-008075cd9c65  dbf2
> /dev/sdd              ocfs2  e278e6c9-d86b-4181-97f4-6c5c61bec7c3  dbf3
> /dev/sde              ocfs2  59451007-df82-49b6-a933-aad1c8b66bcb
> erp01_dbf1
> /dev/sdf              ocfs2  afc39875-a3d4-4192-9ea5-de92cde55a5c  dbf1
> /dev/sdg              ocfs2  4a489f8b-8e82-4026-8ba5-9854f47b3457  dbf1
> /dev/sdh              ocfs2  6a70ae3d-409e-41b6-8f58-415c2963192d
> erp01_dbf2
> /dev/sdi              ocfs2  355d669c-d100-4991-8234-b6c2118f0367  dbf2
> /dev/sdj              ocfs2  de8aed12-c341-45b3-a779-3ccb8a94fb89  dbf2
> /dev/sdk              ocfs2  7e088bf6-3307-468c-87e1-9cc2d48e07dd
> erp01_dbf3
> /dev/sdl              ocfs2  0186f453-5f08-48ea-b43c-0ef622ee6fda  dbf3
> /dev/sdm              ocfs2  5f1458e2-8d82-4328-a13e-ff9f006632c9  dbf3
> /dev/emcpowera        ocfs2  5f1458e2-8d82-4328-a13e-ff9f006632c9  dbf3
> /dev/emcpowerb        ocfs2  0186f453-5f08-48ea-b43c-0ef622ee6fda  dbf3
> /dev/emcpowerc        ocfs2  7e088bf6-3307-468c-87e1-9cc2d48e07dd
> erp01_dbf3
> /dev/emcpowerd        ocfs2  de8aed12-c341-45b3-a779-3ccb8a94fb89  dbf2
> /dev/emcpowere        ocfs2  355d669c-d100-4991-8234-b6c2118f0367  dbf2
> /dev/emcpowerf        ocfs2  6a70ae3d-409e-41b6-8f58-415c2963192d
> erp01_dbf2
> /dev/emcpowerg        ocfs2  4a489f8b-8e82-4026-8ba5-9854f47b3457  dbf1
> /dev/emcpowerh        ocfs2  afc39875-a3d4-4192-9ea5-de92cde55a5c  dbf1
> /dev/emcpoweri        ocfs2  59451007-df82-49b6-a933-aad1c8b66bcb
> erp01_dbf1
> /dev/emcpowerj        ocfs2  e278e6c9-d86b-4181-97f4-6c5c61bec7c3  dbf3
> /dev/emcpowerk        ocfs2  8ddded83-6871-4fff-961e-008075cd9c65  dbf2
> /dev/emcpowerl        ocfs2  016b8942-7176-45d2-bd94-457a34d78550  dbf1
>
>
>
>
> -----Original Message-----
> From: Sunil Mushran [mailto:Sunil.Mushran at oracle.com] 
> Sent: Friday, June 01, 2007 11:01 AM
> To: Kendall, Kim
> Cc: ocfs2-users at oss.oracle.com
> Subject: Re: [Ocfs2-users] ocfs2_fill_super:616 ERROR
>
> This smells like a uuid clash. But it could also be a bug. :)
>
> Do:
> # mount -t debugfs debugfs /debug (if not already mounted)
> # ls -R /debug
>
> In short, the mount is complaining that a entry with the
> same uuid already exists in that location.
>
> If that is the case, do:
> # cat /proc/fs/ocfs2/*/uuid
>
> See if /proc agrees.
>
>
> Kendall, Kim wrote:
>   
>> We are cloning (using EMC symclone) production volumes to refresh 
>> Oracle dev & test environments
>>
>> So far, the cloning is working as expected. I have several cloned 
>> volumes mounted on a couple of systems. Today I tried mounting up a 
>> newly cloned environment and have problems.
>>
>> *_Version Info:_*
>>
>> # cat /etc/redhat-release
>>
>> Enterprise Linux Enterprise Linux AS release 4 (October Update 4)
>>
>> # rpm -qa | grep ocfs2
>>
>> ocfs2-2.6.9-42.0.0.0.1.ELsmp-1.2.3-2
>>
>> ocfs2console-1.2.2-2
>>
>> ocfs2-tools-1.2.2-2
>>
>> *_I've run fsck.ocfs2 against the volume:_*
>>
>> # fsck.ocfs2 -f /dev/emcpowerl
>>
>> Checking OCFS2 filesystem in /dev/emcpowerl:
>>
>> label: dbf1
>>
>> uuid: 01 6b 89 42 71 76 45 d2 bd 94 45 7a 34 d7 85 50
>>
>> number of blocks: 124800000
>>
>> bytes per block: 4096
>>
>> number of clusters: 487500
>>
>> bytes per cluster: 1048576
>>
>> max slots: 4
>>
>> /dev/emcpowerl was run with -f, check forced.
>>
>> Pass 0a: Checking cluster allocation chains
>>
>> Pass 0b: Checking inode allocation chains
>>
>> Pass 0c: Checking extent block allocation chains
>>
>> Pass 1: Checking inodes and blocks.
>>
>> Pass 2: Checking directory entries.
>>
>> Pass 3: Checking directory connectivity.
>>
>> Pass 4a: checking for orphaned inodes
>>
>> Pass 4b: Checking inodes link counts.
>>
>> All passes succeeded.
>>
>> *_Then I try to mount:_*
>>
>> # mount -t ocfs2 /dev/emcpowerl /oradata/erp07/datafiles/1
>>
>> mount.ocfs2: Invalid argument while mounting /dev/emcpowerl on 
>> /oradata/erp07/datafiles/1. Check 'dmesg' for more information on this
>>     
>
>   
>> error.
>>
>> *_Error (from dmesg):_*
>>
>> ocfs2_dlm: Nodes in domain ("016B8942717645D2BD94457A34D78550"): 0
>>
>> (13693,1):ocfs2_fill_super:616 ERROR: Unable to create per-mount 
>> debugfs root.
>>
>> ocfs2: Unmounting device (120,176) on (node 255)
>>
>> I've also made completely sure that all of the other volumes on this 
>> box have had their UUIDs changed so there wouldn't be any UUID 
>> conflicts from newly cloned volumes.
>>
>> Any ideas???
>>
>> The information contained in this E-mail may be confidential and/or 
>> proprietary to Inter-Tel and/or its affiliates. The information 
>> transmitted herewith is intended only for use by the individual or 
>> entity to which it is addressed. If the reader of this message is not 
>> the intended recipient, you are hereby notified that any review, 
>> retransmission, dissemination, distribution, copying or other use of, 
>> or taking of any action in reliance upon this information is strictly 
>> prohibited. If you have received this communication in error, please 
>> contact the sender and delete the material from your computer.
>>
>>
>>     
> ------------------------------------------------------------------------
>   
>> _______________________________________________
>> Ocfs2-users mailing list
>> Ocfs2-users at oss.oracle.com
>> http://oss.oracle.com/mailman/listinfo/ocfs2-users 
>>     
>  
> The information contained in this E-mail may be confidential and/or proprietary to Inter-Tel and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
>   