Re: Filesystem Question

From: Matt_left_coast (not_at_chance.org)
Date: 08/29/04

  • Next message: Matt_left_coast: "Re: Filesystem Question"
    Date: Sat, 28 Aug 2004 16:11:17 -0700
    
    

    Mutant wrote:

    > Matt_left_coast wrote:
    >
    >> Mutant earlier>
    >>> Matt_left_coast wrote:
    >>>
    >>>> Mudisappearte:
    >>>>
    >>>>> Matt_left_coast wrote:
    >>>>>
    >>>>> .... snip....
    >>>>>
    >>>>> I'm still here. Did you say something?
    >>>>
    >>>> Yes, obviously you have no real response to what I have said.
    >>>
    >>> More of the same.....
    >>
    >> Yes, I often repeat the truth.
    >>
    >>>
    >>>>
    >>>> Without the journaling files being written at the time of a crash will
    >>>> probably be corupt and data would be lost, this is the nature of a
    >>>> non-journaling file system like ext2.
    >>>
    >>> So are you saying...."run a journaled system and *when* you crash ( just
    >>> HOW likely is this by the way? )
    >>
    >> Once is enough. Would you tell someone not to back up their system
    >> because a crash is not likely?????? I think not.
    >
    >
    > Yea yea yea one death IS TOO MANY.

    That is right. the same reasons you backup are the same reasons you would
    want to protect the data with a journal file system.

    >

    >
    > I'm gonna cut this and paste it in my editor so that in the event of a
    > crash it'll save what I am working on. Cause as it is right now... the
    > shit is toast.
    >

    meaningless bable. It would not be tost because it is alread archived on
    usenet, guess you are to stupid to understand that usenet and writing to a
    drive are two different things.

    >>
    >> In the event of a crash, the journaling file system DOES reduce your
    >> recovery time DRASTICLY. ext2 on a large file system can take HOURS to
    >> recover, no business wants their systems down for hours. I don't what my
    >> desktop to take hours to recover. Not when a jornaling file system can
    >> the system back up and running in a mater of minutes. From the link I
    >> posted before:
    >>
    >> http://www.linuxformat.co.uk/archives/LXF25.tut_ext3.pdf
    >>
    >> begin quote
    >>
    >> In this way, in the unlucky event of an unclean shutdown the file system
    >> recovery process passes through the analysis of the journal and usually
    >> takes a few seconds, even on large disks, while it can take some hours
    >> with the traditional fsck (file system check) of the ext2 file system.
    >> For that reason, journaling is mainly important where after an unclean
    >> shutdown the system must be back on track as soon as possible, but can
    >> save quite a bit of time even for the desktop.
    >>
    >
    > Get rid of that shit I mentioned earlier et al and watch your system
    > "crashes" disappear.

    So you are saying ALL system crashes are related to ext3?????? I don't think
    so. Please provide SPECIFIC proof of instablility of ext3.

    > This line of thought reminds me of a doctor
    > prescribing a pill to take care of the ill effects of another pill he has
    > prescribed. If you want to.... hey!
    >

    I see no relationship.

    >
    >
    >>> Cause that's what
    >>> I'm reading. And yet that can't be what you are asking cause it ain't
    >>> true.
    >>>
    >>
    >> Prove it. I have supplied documentation in suport of my claims, can you
    >> do the same for yours, or are you going to just keep crying?
    >>
    >
    > http://www.slashdot.org search "filesystem" "file systems"
    >

    If you can't find specific facts to back up your claims, I'm not going to
    look. Provide specific proof to back up your claims.

    >
    >
    >
    >>>>
    >>>> Read and learn:
    >>>
    >>> That is exactly how I've learned all that I know... if you don't count
    >>> poddy training.
    >>
    >> I see you can not actualy address the points in the article.
    >>
    >>>
    >>>>
    >>>> http://www.linuxformat.co.uk/archives/LXF25.tut_ext3.pdf
    >>>>
    >>>> I'll bet all you can do is cry about "company line" without supplying
    >>>> ANYTHING to show were the "company line" is faulty or wrong. Put up or
    >>>> shut up.
    >>>
    >>> Cry? I just here.... now.... helping my open source brothers!
    >>
    >> So, why can't you address the points rasied with supporting, factual
    >> documentation? Do you anything that supports your claim.
    >>
    >>>
    >>> What is your purpous (sp) here?
    >>
    >> The truth.
    >>
    >
    >
    > Not with that talk.

    Yeah, your unsuported claims dose muttle the truth, but it does give the
    rest of us the oportunity to get the true facts out:

    http://www.linuxformat.co.uk/archives/LXF25.tut_ext3.pdf
    http://puggy.symonds.net/~rajesh/howto/ext3/ext3-2.html

    No flawed analogyies about doctors and pills form me!

    >
    >>>
    >>>
    >>> - Peace -
    >>> Mutant
    >
    >
    >
    >
    > --


  • Next message: Matt_left_coast: "Re: Filesystem Question"

    Relevant Pages

    • Re: Filesystem Question
      ... I often repeat the truth. ... > Using the ext3 file system can provide stronger guarantees about data ... > In the event of a crash, the journaling file system DOES reduce your ... > recovery time DRASTICLY. ...
      (alt.linux)
    • Re: Filesystem Question
      ... I often repeat the truth. ... >> Without the journaling files being written at the time of a crash will ... Using the ext3 file system can provide stronger guarantees about data ... recovery time DRASTICLY. ...
      (alt.linux)
    • Re: Can extra processing threads help in this case?
      ... against a OS crash that overwrites the wonderfully ... Shall I tell my set of Unix ... linux has a file system; ... problem with priority inversion. ...
      (microsoft.public.vc.mfc)
    • Re: Can extra processing threads help in this case?
      ... I fail to see why either one matters if you have a fully-transacted file system. ... against a OS crash that overwrites the wonderfully ... Shall I tell my set of Unix ... problem with priority inversion. ...
      (microsoft.public.vc.mfc)
    • XP randomly restarts on me
      ... this could be either virus related or hardware. ... might also be the drivers for you graphics card are not ... >kind of crash where you get to close the frozen program ... >check the file system on my C drive for errors. ...
      (microsoft.public.windowsxp.general)