Building Out XenServer 6.5 with USB Boot and Software RAID 10
-
The issue is that logging on XenServer doesn't just stop. So Maintenance is critical.
You don't want to auto-dump your logs, you might have issues that you want to look into to. So keeping them around somewhere is critical.
-
@DustinB3403 said:
The issue is that logging on XenServer doesn't just stop. So Maintenance is critical.
You don't want to auto-dump your logs, you might have issues that you want to look into to. So keeping them around somewhere is critical.
Oh I wasn't saying to stop logging, I just wondered if it was a possibility to run it in RAM. More of just an inquisitive qustion.
-
You CAN run in RAM. But why? If anything happens the logs vanish. And it uses up memory too, but not normally all that much. But will you have it auto-rotate in some way?
-
Completing the Resync process takes a very long time.....
-
It'll do that
-
@scottalanmiller said:
You CAN run in RAM. But why? If anything happens the logs vanish. And it uses up memory too, but not normally all that much. But will you have it auto-rotate in some way?
I was just wondering if it's possible to do it similarly to VMware. It was more of just a question for questions sake. XenServer already takes up a gig of ram so the rest couldn't be that much. And you could send the logs somewhere else like you mentioned. It was more of just a question to see if it was possible.
-
You can always create a ram disk and put anything there that you want.
-
Just did a reboot on my test system, and the RAID Array is unmounted. Meaning we need to add it to fstab.
-
I reboot without a problem, and the mounting of the array is managed properly by xen without the entry in fstab.
-
On the test setup I built using the OP, the array is lost.
Along with everything on it. It's much safer to keep it stored in fstab..
-
Lost the whole array? That's strange that would imply something went really wrong. The entry added in fstab whould only cause the os to automount the array, nothing there should cause the array itself to get wiped.
What is the current status of your array?
mdadm --detail /dev/md0
cat /proc/mdstat -
This is what is in /var/run/sr-mount....
-
This is mdadm --details
-
and cat /proc/mdstat
-
@DustinB3403 said:
and cat /proc/mdstat
patience.....
-
Yes Yes, you're too quick some times sir. I corrected it.
-
So with the above 3 pictures and the Array missing.
I'd obviously have to rebuild the array, and remap items. Additionally, I'll have to recreate my "backup" USB (which isn't a huge deal)
-
@DustinB3403 can you run
mdadm --examine --scan
-
We need to find the missing array before we can do anything else. As @romo mentioned we need to scan and see if the array is out there somewhere.
-
