All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Schenkewitz <Dirk.Schenkewitz@interface-ag.com>
To: flx@msu.ru
Cc: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: trolling
Date: Wed, 12 Feb 2003 13:32:07 +0100	[thread overview]
Message-ID: <3E4A3EC7.66AD22C8@interface-ag.com> (raw)
In-Reply-To: 20030212131120.A10438@t-raenon.nmd.msu.ru

Hello Mr. Lyamin,

Alexander Lyamin schrieb:
> 
> Once, back in 1990, I had one customer calling and blaming me
> that we sold them BAD crt, where only LEFT part of screen being
> not displaying everything. Being upset (CRT's were expensive
> in thouse days) I went to his office only to realise that this
> person used Norton Commander shell and pushed Ctrl+F1 effectively
> turning off left panel....
> 
> He was IGNORANT, but his rage and HATRED were so PURE.

:-) Well, I can understand both viewpoints, I have been on both
sides - right now I must be on a troll's side.

> You see, for IGNORANT people its much easier to blame someone else
> then their ignorance.

I'm aware of my ignorance, really. At least a bit. But, see, in
that case it was not much loss to just forget the filesystem, and
it was EASIER for me to give ext3 a try than to go to someone else 
and search the internet for a solution - I had no internet access
by myself back then.

> P.S. "In addition, check your facts before making a statement that
> insults someone and claims something that is completely untrue."
>
> Powersupply units physically damaging hard-drive disks (plates!).

Well, I'm not sure what EXACTLY happened. Somehow I got suspicious
about the power supply, put in a new one, and from there on, every-
thing was fine. Then I checked the disk, a few tracks seemed to be
damaged, they turned out to be unrelieable. I modified the partitions
so that these tracks were left out. (The disk ist still in use today.)
Again, I'm not sure, but I believed the bad power made the disk slow
down or have the head land or something else while working in that
area. I believed that the journal area was the one which got most of
the traffic, so I thought it was logical that it got most of the
damage. The same was true for the ext3-journal area - both journals
got corrupted.

> Unwillingness of running FSCK when its known that filesystem was 
> physically corrupted.

I was not really unwilling - I was too stupid to find one on my
system and on my CDs. :-/

> EXT2 never runned fsck in YEARS (what about mountcount flag? :).

Er... did I say that? Sorry, that's wrong. In fact, fsck.ext3 ran
every time the system was bootet, but normally it only replays the
journal (if needed), unless the actual number of mounts exceed the
max-mounts, as you say. Admittedly, it is a pain to wait several
minutes to let that finish. I tuned my system (by adjusting the
max-mountcount values and the mountcount values) so that no more
than one partition is "really" fsck'd per boot. (*Sigh*)

That's one reason why I'm here!

Thanks for answering a troll :-) - happy coding
	dirk
-- 
Dirk Schenkewitz 

InterFace AG                 fon: +49 (0)89 / 610 49 - 126
Leipziger Str. 16            fax: +49 (0)89 / 610 49 - 83
D-82008 Unterhaching         
http://www.interface-ag.de   mailto:dirk.schenkewitz@interface-ag.de

  reply	other threads:[~2003-02-12 12:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11 18:59 Corrupted/unreadable journal: reiser vs. ext3 Dirk Schenkewitz
2003-02-11 20:27 ` Hans Reiser
2003-02-11 21:30   ` Mike Hodson
2003-02-11 21:47     ` Hans Reiser
2003-02-11 21:58     ` Hans Reiser
2003-02-12  6:35       ` Oleg Drokin
2003-02-11 23:11     ` Adam Goryachev
2003-02-11 23:17       ` Anders Widman
2003-02-12  0:12         ` Hans Reiser
2003-02-12 10:23           ` Anders Widman
2003-02-12 10:47             ` Hans Reiser
2003-02-12 11:12               ` Adam Goryachev
2003-02-12 13:42                 ` Anders Widman
2003-02-12 14:15                   ` Russell Coker
2003-02-12 15:26                     ` Anders Widman
2003-02-12 16:22                       ` bscott
2003-02-12 16:28                       ` Russell Coker
2003-02-12 16:40                         ` Anders Widman
2003-02-13  3:42                       ` Zygo Blaxell
2003-02-13 10:13                         ` Anders Widman
2003-02-13 14:44                           ` Rudy Zijlstra
2003-02-13  3:31                     ` Zygo Blaxell
     [not found]                       ` <20030213113003.7ee7af6e.philippe.gramoulle@mmania.com>
2003-02-13 18:17                         ` rijndael loopback encryption was [Re: Corrupted/unreadable journal: reiser vs. ext3] Zygo Blaxell
2003-02-12 16:39                 ` Corrupted/unreadable journal: reiser vs. ext3 Sam Vilain
2003-02-12  5:12         ` Ross Vandegrift
2003-02-12  7:17         ` Oleg Drokin
2003-02-12 10:17         ` Alexander Lyamin
2003-02-12 10:19           ` Alexander Lyamin
2003-02-12 16:25         ` Vitaly Fertman
2003-02-12 16:56           ` Anders Widman
2003-02-12 17:13             ` Oleg Drokin
2003-02-12  1:02       ` Mike Hodson
2003-02-12  7:25         ` Oleg Drokin
2003-02-12  9:45         ` Hans Reiser
2003-02-12 16:09         ` Sam Vilain
2003-02-12 10:11 ` trolling Alexander Lyamin
2003-02-12 12:32   ` Dirk Schenkewitz [this message]
2003-02-12 14:48   ` trolling Chris Mason
2003-02-13 19:54   ` trolling Zygo Blaxell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E4A3EC7.66AD22C8@interface-ag.com \
    --to=dirk.schenkewitz@interface-ag.com \
    --cc=flx@msu.ru \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.