05-23-2022 01:56 PM
I have 2 9516 switches in a SWV stack. "show switches" output shows that the switches are stacked and the active switch in the stack is as expected.
SW1#show file systems
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - opaque rw system:
- - opaque rw tmpsys:
1651314688 1547587584 disk rw crashinfo: crashinfo-1:
1651507200 1563426816 disk rw crashinfo-2: stby-crashinfo:
* 11353194496 9935884288 disk rw flash: flash-1:
11353980928 9936306176 disk rw flash-2: stby-flash:
"show file systems" shows that the flash: and flash-2: file systems are available and have nearly the same usage/remaining space. However if I execute a directory command on flash:
SW1#dir flash:
Directory of flash:/
No files in directory
11353194496 bytes total (9935884288 bytes free)
But if I execute a directory on flash-2:
SW1#dir flash-2:
Directory of flash-2:/
409602 -rw- 2097152 May 16 2022 17:34:05 -04:00 nvram_config
409603 -rw- 2097152 May 16 2022 17:34:05 -04:00 nvram_config_bkup
.
.
.
11353980928 bytes total (9936306176 bytes free)
Additionally, if I try an operation on the flash: filesystem, like trying to create a directory, I get an I/O error.
To my knowledge, the file systems on these switches were in sync & operating correctly when the stack was created about a year ago. Can anyone suggest any additional troubleshooting I can do to figure out what's going on here? The stack is in production, so it would be better if it did not have to be rebooted.
05-23-2022 03:23 PM
"dir flash" should show the content of flash1 and 2. What is the output of "dir"?
Maybe you are hitting a bug. Is this causing any operational issues?
HTH
05-23-2022 03:45 PM - edited 05-23-2022 03:49 PM
"show file systems" shows flash: and flash-1: mapped to the same filesystem, so:
SW1#dir
Directory of flash:/
No files in directory
11353194496 bytes total (9935884288 bytes free)
The issue right now is that I can't create a directory and/or copy any files to the flash on this switch. The other concerning thing is that the boot variable is pointing to flash:packages.conf so I'm not sure what will happen if this stack gets rebooted for some reason while it's in this state.
05-23-2022 04:08 PM
Post the complete output to the following commands:
05-25-2022 06:28 AM
Looks like we might be hitting this bug even though its supposedly resolved in our IOS-XE release. Same exact messages rolling in the log.
05-25-2022 06:43 AM
Yes, most likely you need to upgrade to a different version. I would open a ticket with TAC and ask them for a version recommendation.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide