Hi Walter 

I had the same problem with both files.  I also thought that maybe the bundle  was corrupted so I download again the file and still had the problem. 

The current version is 2.2.6c

Regards,

Debbie 

Greetings.

You can also see 'sync/copy' issues if there are file system issues on the destination (subordinate) FI.

Please confirm you have plenty of space in bootflash on that FI.  You may also want to connect to the nxos on that FI and run the following:

#show logging log | in ext3|inode

#show logging nvram | in EXT3

If you do see something regarding 'ext3 file system error' or 'ext3_new_inode: IO failure' then you will want to contact TAC as they will need to boot the FI into basic boot loader, along with dplug file, so a file system check can be run.

Thanks,

Kirk...

Hi Kirk,

Both FI have 25% of used. 

I run the commnad you mention and I get the following output. 

2017 Jul 21 09:23:37 USFQ-FI-A-B Jul 21 09:23:37 %KERN-2-SYSTEM_MSG: [26352191.378957] EXT3-fs error (device sda3): ext3_add_entry: bad entry in directory #752200: rec_len is too small for name_len - offset=272, inode=719724, rec_len=36, name_len=44 - kernel

So what I understand is that I need to opend a case with TAC.

Regards,

Debbie 

Greetings.

Yes, basically TAC will install a special dplug file, and reboot the FI (will need console connection), break into the boot loader sequence, early enough before file systems are mounted so e2fsck can be run to check/repair the ext3 file system.

Thanks,

Kirk...

Did TAC help you get the FI file system Issues resolved?

Thanks,

Kirk...

Hi Kirk, 

I opend a case with TAC. 

They couldnt  upload the debug plugin onto FI B so they need to rebuild the switch to attempt to fix out the corrupted partition.

We are planning the maintenance window for next monday. I would let you know how it go. 

Regards,

Debbie