On Thu, 2009-02-12 at 23:56 +0300, Andrew Junev wrote:
> P.S. What does the 'OP' mean? Something like 'Original Poster'? :)
Yes, it's accepted usage. Not that common but not extremely rare either.
poc
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mai
Thursday, February 12, 2009, 11:29:07 PM, you wrote:
> In any case, it would be interesting to have the OP reboot, and see
> if the VG is active on reboot.
I did. I even powered the system down. It starts now without that
problem and everything gets mounted automatically during boot.
So the probl
Mikkel L. Ellertson wrote:
Strange - /var/lock/lvm is empty, and its date does not correspond
It's always empty unless an LVM tool is running (or you've disabled
locking or are using some non-local locking mode for all your VGs).
Try running e.g. vgchange in a debugger. Set a breakpoint on
Bryn M. Reeves wrote:
> Mikkel L. Ellertson wrote:
>> Bryn M. Reeves wrote:
>>> Mikkel L. Ellertson wrote:
Andrew Junev wrote:
> What shall I do to automatically activate this VG during
> boot?
>
If I understand the VG commands correctly, you just did.
>>> I think the OP wants
Mikkel L. Ellertson wrote:
Bryn M. Reeves wrote:
Mikkel L. Ellertson wrote:
Andrew Junev wrote:
What shall I do to automatically activate this VG during
boot?
If I understand the VG commands correctly, you just did.
I think the OP wants his VG to activate without the need for him
to give th
Bryn M. Reeves wrote:
> Mikkel L. Ellertson wrote:
>> Andrew Junev wrote:
>>>
>>> What shall I do to automatically activate this VG during boot?
>>>
>> If I understand the VG commands correctly, you just did.
>
> I think the OP wants his VG to activate without the need for him to
> give the root p
Andrew Junev wrote:
/var/log/messages doesn't contain any information about that problem.
The error happened too early during boot - so that the data didn't get
into the log files (disks were mounted in read-only mode).
You can work around this by commenting out the file systems on the
problem
Hello Bryn,
> You need to understand why it wasn't being activated automatically.
> Boot logs (dmesg and/or /var/log/messages) would help here. Normally,
> devices are scanned for LVM metadata when rc.sysinit runs.
> There were some bugs in older releases (f8 is no longer
> supported/maintained)
Mikkel L. Ellertson wrote:
Andrew Junev wrote:
Thursday, February 12, 2009, 9:42:38 PM, you wrote:
Running the command: vgchange -ay VolTerabytes00 Should
activate the VG, assuming that all PVs are present (and any
needed modules have been loaded).
I tried running lvm and it says "Locking t
On Thu, 2009-02-12 at 19:09 +, Bryn M. Reeves wrote:
> There were some bugs in older releases (f8 is no longer
> supported/maintained) where udev would not wait long enough for some
> devices to appear, causing these scans to "miss" the VG. That sounds
> plausible here since the vgchange -ay w
Andrew Junev wrote:
> Thursday, February 12, 2009, 9:42:38 PM, you wrote:
>
>
>> Running the command:
>
>> vgchange -ay VolTerabytes00
>
>> Should activate the VG, assuming that all PVs are present (and any
>> needed modules have been loaded).
>
>>> I tried running lvm and it says "Locking ty
Andrew Junev wrote:
Thursday, February 12, 2009, 9:42:38 PM, you wrote:
Running the command:
vgchange -ay VolTerabytes00
Should activate the VG, assuming that all PVs are present (and
any needed modules have been loaded).
I tried running lvm and it says "Locking type 1 initialisation
Thursday, February 12, 2009, 9:42:38 PM, you wrote:
> Running the command:
> vgchange -ay VolTerabytes00
> Should activate the VG, assuming that all PVs are present (and any
> needed modules have been loaded).
>> I tried running lvm and it says "Locking type 1 initialisation failed"
>> no mat
Andrew Junev wrote:
I'm prompted to enter a root password to get to system maintenance, or
Ctrl+D to continue.
In the system maintenance I can see there's /dev/VolGroup00 but
there's no /dev/VolTerabytes00, so my newly-created VG seem to be
missing!
Running the command:
vgchange -ay VolTeraby
Hello All,
I have a MythTV system running on Fedora 8. Initially the system only
had one VolumeGroup: VolGroup00. Later on I added two more physical
drives and created a completely new VolumeGroup (VolTerabytes00) to
store all my data. This setup used to work fine for about a month.
Today I switc
15 matches
Mail list logo
