How to Stop XenServer from Mounting /var/log
-
@travisdh1 said i
Ah, I gotcha. Yeah, shouldn't be a problem. Bug report time I'd say.
I mean this is what I am doing. Is it possible any of these steps could be hosing something else?
- dd the line in fstab that mounts /var/log
- reboot the host
- once the server comes back up it is logging to the "normal" spot
- stop rsyslog
- del /var/log
- mkdir in /run/sr-mount/xxxxx called xenserverlogs
- symlink /var/log to that folder from #6
- restart rsyslog
After doing these steps, the logging is working perfectly to the folder in #6.
Sometime (I think it might be around midnight) it seems to crash on reboot and not come back up. The PV lists in pvs and lvs but is not in /dev/mapper or listed under /dev/dm* I also lose networking
See anything odd?
-
@BRRABill The only thing that springs to mind is making sure the volume group the logical volume sits on is ok. It should be with the logical volume being ok. The other thing is making sure /var/log is mounting via fstab correctly (df). Kinda grasping at straws at the moment.
-
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@BRRABill The only thing that springs to mind is making sure the volume group the logical volume sits on is ok. It should be with the logical volume being ok. The other thing is making sure /var/log is mounting via fstab correctly (df). Kinda grasping at straws at the moment.
The VG/LV should be OK. They are brand new and work fine until the change.
I do not mount /var/log ... just symlink to it. Is that incorrect? It is originally in fstab because they mount it to a partition on the boot device.
-
@BRRABill said in How to Stop XenServer from Mounting /var/log:
I do not mount /var/log ... just symlink to it. Is that incorrect? It is originally in fstab because they mount it to a partition on the boot device.
Your goal is to not mount /var/log as its own filesystem, that is correct.
-
@scottalanmiller said
Your goal is to not mount /var/log as its own filesystem, that is correct.
@scottalanmiller What is your take on this new wrinkle?
-
@BRRABill Did you create a separate logical volume for /var/log, or is both that and the storage repository on the same lv?
-
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@BRRABill Did you create a separate logical volume for /var/log, or is both that and the storage repository on the same lv?
No. XS used 100% of the space I had for its own LV.
So we thought putting a directory with the VHD files would be ok.
So /run/sr-mount/xxxxxxxxx
has
vm1.vhd
vm2.vhd
vm3.vhd
lost+found
xenserverlogs (the directory i created)Is it possible putting a directory there would cause this big an issue?
-
possible, yes. I'd say unlikely, but if it causes the software to freak out because it doesn't expect it there, yes.
-
@BRRABill said in How to Stop XenServer from Mounting /var/log:
Is it possible putting a directory there would cause this big an issue?
In no way should it create issues like this... in the real world however, well.
Do you have free space available that you could shrink the LV and create another LV just for the log files?
-
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@BRRABill said in How to Stop XenServer from Mounting /var/log:
Is it possible putting a directory there would cause this big an issue?
In no way should it create issues like this... in the real world however, well.
Do you have free space available that you could shrink the LV and create another LV just for the log files?
yes, shrinking is a technical possibility.
-
@scottalanmiller said in How to Stop XenServer from Mounting /var/log:
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@BRRABill said in How to Stop XenServer from Mounting /var/log:
Is it possible putting a directory there would cause this big an issue?
In no way should it create issues like this... in the real world however, well.
Do you have free space available that you could shrink the LV and create another LV just for the log files?
yes, shrinking is a technical possibility.
The other question I'd think about is if it's an LV or VG. ProxMox (good riddance, it's gone) actually uses a volume group when you mount local storage LVM containers.
-
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@scottalanmiller said in How to Stop XenServer from Mounting /var/log:
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@BRRABill said in How to Stop XenServer from Mounting /var/log:
Is it possible putting a directory there would cause this big an issue?
In no way should it create issues like this... in the real world however, well.
Do you have free space available that you could shrink the LV and create another LV just for the log files?
yes, shrinking is a technical possibility.
The other question I'd think about is if it's an LV or VG. ProxMox (good riddance, it's gone) actually uses a volume group when you mount local storage LVM containers.
You have to have a VG to have an LV.
-
@scottalanmiller said in How to Stop XenServer from Mounting /var/log:
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@scottalanmiller said in How to Stop XenServer from Mounting /var/log:
@travisdh1 said in How to Stop XenServer from Mounting /var/log:
@BRRABill said in How to Stop XenServer from Mounting /var/log:
Is it possible putting a directory there would cause this big an issue?
In no way should it create issues like this... in the real world however, well.
Do you have free space available that you could shrink the LV and create another LV just for the log files?
yes, shrinking is a technical possibility.
The other question I'd think about is if it's an LV or VG. ProxMox (good riddance, it's gone) actually uses a volume group when you mount local storage LVM containers.
You have to have a VG to have an LV.
Right. In this case what they did actually does make sense. The drive containers were each created as their own LV.
-
@travisdh1 said
Right. In this case what they did actually does make sense. The drive containers were each created as their own LV.
You mean what XS did makes sense?
-
@BRRABill said in How to Stop XenServer from Mounting /var/log:
@travisdh1 said
Right. In this case what they did actually does make sense. The drive containers were each created as their own LV.
You mean what XS did makes sense?
I was referring to ProxMox with that comment, but XS does the same thing with LVM local storage.
-
@travisdh1 said
dd would take a long, long time if you have it copying something like /proc, /sys, or /dev.
Is it "safe" to run dd on a running boot disk? Why does it take so long?
Assuming so, but you know what happens when one assumes!
-
@BRRABill said in How to Stop XenServer from Mounting /var/log:
@travisdh1 said
dd would take a long, long time if you have it copying something like /proc, /sys, or /dev.
Is it "safe" to run dd on a running boot disk? Why does it take so long?
Assuming so, but you know what happens when one assumes!
Yes, it is only reading, not writing. Reading things is always safe.
-
@scottalanmiller said
Yes, it is only reading, not writing. Reading things is always safe.
Why does it take so long for those directories?
-
@BRRABill said in How to Stop XenServer from Mounting /var/log:
@scottalanmiller said
Yes, it is only reading, not writing. Reading things is always safe.
Why does it take so long for those directories?
dd reads block devices, not directories. It has no concept of directories.
-
@scottalanmiller said
dd reads block devices, not directories. It has no concept of directories.
Then what is the significance/reason for the previous poster saying
"dd would take a long, long time if you have it copying something like /proc, /sys, or /dev."
