Bug? - Mandriva

This is a discussion on Bug? - Mandriva ; Greetings On Mandriva 2007 Spring, both x86_64 and i586 Installed partitions using "expert mode" and "auto allocate". This give 6 partitions: "/", swap, /usr, /var, /home and /tmp.Ideal for upgrading as you only have to install "/" and /usr. However, ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Bug?

  1. Bug?

    Greetings
    On Mandriva 2007 Spring, both x86_64 and i586
    Installed partitions using "expert mode" and "auto allocate".
    This give 6 partitions:
    "/", swap, /usr, /var, /home and /tmp.Ideal for upgrading as you only have
    to install "/" and /usr.
    However, on this version (2007 Spring) after doing any upgrades, I have
    found my /var partition is unrecognised. If you look at it from konqueror
    it is there, with all its folders, yet if you do a new installation, using
    existing partitions, /var is not recognised and shows a blank partition.

    Has anyone noticed this?
    Has it been previously reported?
    Does anyone know what causes it?

    Any info will be appreciated

    --
    Rgds.
    Edward
    Registered Linux User No. 224802

  2. Re: Bug?

    On Tue, 22 May 2007 19:17:27 -0400, Edward wrote:
    > Installed partitions using "expert mode" and "auto allocate".
    > This give 6 partitions:
    > "/", swap, /usr, /var, /home and /tmp.Ideal for upgrading as you only have
    > to install "/" and /usr.
    > However, on this version (2007 Spring) after doing any upgrades, I have
    > found my /var partition is unrecognised. If you look at it from konqueror
    > it is there, with all its folders, yet if you do a new installation, using
    > existing partitions, /var is not recognised and shows a blank partition.


    I'm not clear on what you mean by "unrecognized" From what you have described,
    I suspect you created the /var partition, formatted it, but forgot to mount it,
    in which case the install would have put all of the contents of /var, into the
    root (/) filesystem.

    Try the following (as root) ...
    Edit your /etc/fstab, to ensure the filesytem you want to have /var stored in,
    will be mounted as /var, on the next mount.
    # telnet 1 #, to stop all processes that might be using /var
    # mount /usr # to ensure access to programs like mc, tar, etc.
    # umount /var # just to make sure it's not mounted
    # mv /var /vardata
    # mkdir /var
    # mount /var
    # cd /vardata
    # tar cfp - . | (cd /var && tar xpf -) # to copy the data to the new filesystem
    # telinit 3, to return to run level 3

    After ensuring /var is ok, delete the directory /vardata, and all of it's contents.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  3. Re: Bug?

    David W. Hodgins wrote:

    > On Tue, 22 May 2007 19:17:27 -0400, Edward
    > wrote:
    >> Installed partitions using "expert mode" and "auto allocate".
    >> This give 6 partitions:
    >> "/", swap, /usr, /var, /home and /tmp.Ideal for upgrading as you only
    >> have to install "/" and /usr.
    >> However, on this version (2007 Spring) after doing any upgrades, I have
    >> found my /var partition is unrecognised. If you look at it from konqueror
    >> it is there, with all its folders, yet if you do a new installation,
    >> using existing partitions, /var is not recognised and shows a blank
    >> partition.

    >
    > I'm not clear on what you mean by "unrecognized" From what you have
    > described, I suspect you created the /var partition, formatted it, but
    > forgot to mount it, in which case the install would have put all of the
    > contents of /var, into the root (/) filesystem.
    >
    > Try the following (as root) ...
    > Edit your /etc/fstab, to ensure the filesytem you want to have /var stored
    > in, will be mounted as /var, on the next mount.
    > # telnet 1 #, to stop all processes that might be using /var
    > # mount /usr # to ensure access to programs like mc, tar, etc.
    > # umount /var # just to make sure it's not mounted
    > # mv /var /vardata
    > # mkdir /var
    > # mount /var
    > # cd /vardata
    > # tar cfp - . | (cd /var && tar xpf -) # to copy the data to the new
    > # filesystem telinit 3, to return to run level 3
    >
    > After ensuring /var is ok, delete the directory /vardata, and all of it's
    > contents.
    >
    > Regards, Dave Hodgins
    >

    Greetings,
    Thanks for your reply.
    On re-installing and selecting "Use existing partitions" they are all shown
    up, with the various names, ie. /, /usr, (where /var should be is now in
    blank), /home and /tmp.
    In other words, /var is no longer recognised.
    This causes the computer to run slow.
    It seems to happen after installing the updates.

    I have just check my PC (x86_64) now and find /var is no longer there. (I am
    writing this on my notebook (i586) now although I have encountered this
    problem in my notebook too)

    Hope this clarifies.

    I will try your suggestion, before going for a re-install.
    Will advise on results
    --
    Rgds.
    Edward
    Registered Linux User No. 224802

  4. Re: Bug?

    On Wed, 23 May 2007 17:21:00 -0400, Edward wrote:

    > On re-installing and selecting "Use existing partitions" they are all shown
    > up, with the various names, ie. /, /usr, (where /var should be is now in
    > blank), /home and /tmp.
    > In other words, /var is no longer recognised.


    If I'm correct, in the initial allocations, that the /var partition was not
    mounted, then diskdrake would not have included a line for it when it saved
    /etc/fstab.

    Future executions of diskdrake would just see an empty partition, with no
    name, or mount point associated (those come from fstab, or mtab, if already
    mounted).

    > This causes the computer to run slow.


    Having /var in the / filesystem should not impact the computer's speed.
    as long as / doesn't get full.

    > I will try your suggestion, before going for a re-install.
    > Will advise on results


    Regards, Dave Hodgins


    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

+ Reply to Thread