file, or
maybe two files at several hundred MB each. CD Images, Debian 2.2r5 in
my case.
--
Matthias Andree
GPG encrypted mail welcome, unless it's unsolicited commercial email.
y partition? I presume, not too much.
--
Matthias Andree
GPG encrypted mail welcome, unless it's unsolicited commercial email.
MB/s.
>
> Is DMA, unmask IRQ, read ahead and similar activated?
SCSI here, with aic7xxx 5.x and 6.x driver, no particular tuning in
place except that I told the AHA2940 to negotiate Ultra-Wide, it has
braindead default settings (negotiates 10 MXfers/s only, no Ultra), so
we can safely assume it
still get 86% out.
However, I hope to be able to play with the settings later, to figure
what's going on there.
--
Matthias Andree
GPG encrypted mail welcome, unless it's unsolicited commercial email.
ly, writing the bad blocks will make the drive remap them
if it has spare sectors left to remap to.
--
Matthias Andree
s, fsync() only returns after all blocks are
on disk. While I'm not sure if and if yes, which, Linux file systems are
affected, but for portable applications, be aware that sync() may return
prematurely (and is allowed to!).
--
Matthias Andree
e, trafficmagnet.net. They will come back.
(They come back to haunt the university site that I administer, I
regularly see rejects in my mailer's log file.)
--
Matthias Andree
correctableError }, LBAsect=9641711
Your drive is broken. Such things can happen for a block or two after
power failure in the mid of a write process and will then go away the
next time the block is written again. What drive type is this? (to find
that out, use: cat /proc/ide/hda/model)
--
Matthias Andree
well (IBM-DTLA-307045, FUJITSU MPE3136AH) on
> different PCs with Intel and Via motherboards.
It's not "dma" but the "unrecoverable error" part that matters. The DMA
trips over as consequence of this defective block (there is no data that
could be transferred), the DMA is *not* the cause for the bad block.
--
Matthias Andree
he super block, much
like ext2 stores the "file system with errors" condition.
--
Matthias Andree
ched that to do
ARWE. IDE users are not too lucky unless their vendor provides them with
a tool (and not many ship raw floppy images, many have some multi-MB
Windoze tools just to write some hundred kByte to a floppy disk...)
--
Matthias Andree
ff directly in the drive rather than through all
the kernel buffers, and can also refresh or reassign bad blocks.
--
Matthias Andree
lives, so it is good to educate them with URLs
> and other references at the time they run fsck.
A propos URL, here we go:
ftp://ftp.fokus.gmd.de/pub/unix/sformat/
--
Matthias Andree
|
1 pointer
[ 368032]
---
| 13|13010 13034 0x1001 DRCT (2), len 136, location 1199 entry count 65535, fsck need
|0, format old|
===
--
Matthias Andree
On Thu, 29 Aug 2002, Vitaly Fertman wrote:
> Could you try reiserfsck --fix-fixable from reiserfsprogs-3.6.4-pre1, these
> fixable corruptions seem to be fixed there, and then reiserfsck --check.
I did this.
I don't recall if I got the dirty buffer thingy (I was sort of busy,
with ISDN PBX br
ugh the problems really escaped reiserfsck v3.6.3
but no more v3.6.4-pre1.
I'll check your kernel's changelog to get the fix though.
--
Matthias Andree
em, regardless of ext3
or reiserfs.
Of course, write caches must be turned of or write barrier patches be
applied to be safe in case of a power blackout.
--
Matthias Andree
rybody talks about it, nobody explains. or did I miss something?
You can safely consult ext3 documentation on these options, reiserfs
should behave the same in respect to these options.
--
Matthias Andree
> noatime are shown.
This also affects ext3fs. Leaving full quote and posting to linux-kernel
as well.
--
Matthias Andree
post about code size and execution speed: it's not
generally true that larger code is also slower. It depends how that code
is arranged. If you have many abstractions, then maybe it's slower. If
you have many specialized functions in an otherwise flat profile, it can
be a good deal faster than
codes that (e2)fsck uses?
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
xes
recently.
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
1 b530
080541cc b530 08060828 b258 00c4 002b 002b 00c4
Call Trace:[sys_lstat64+129/144] [system_call+51/56]
Call Trace:[] []
Code: Bad EIP value.
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
On Tue, 20 Jan 2004, Matthias Andree wrote:
> This happened during the nightly updatedb, which calls find. The hex
> string is "resi", "locate resi" finds a file in a reiserfs file system,
> /usr.
>
> reiserfsck 3.6.11 afterwards fixed some
> vpf-10680:
EXCL doesn't work across NFS anyways, workaround: use mkstemp(2) and
link(2).
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
rebuild.log.gz
Description: gzipped reiserfsck --rebuild-tree log
D for instance), it can royally
screw up your file system. Beyond repair, to a "use your backup" state.
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
ux and a POSIX version.
Or am I barking up the wrong tree?
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
d 2.2.19 (on
http://www.linux.org.uk/ somewhere).
--
Matthias Andree
add noauto to the fstab options to prevent mount on boot.
See man fstab.
--
Matthias Andree
d,
the "check if your file's st.n_link has increased to 2, if so, your link
has succeeded" could be avoided.
Not sure if Coda or AFS have concepts like these.
--
Matthias Andree
out troubles. Been there, done that,
had success.
linux-kernel had reports NFSv3 was reliable from XFS 1.0; as to the
performance, go out and figure on your own.
--
Matthias Andree
ectory, what can happen? Say I rename the file,
> and then I pull the plug on my computer. Can the file be gone? Will it
> have the old name?
It may be gone, it may be there with wrong contents, it may end up in
lost+found if you fsynched the file but not the directory. Nasty things.
--
Matthias Andree
ramming a certain way,
> they will start using it. "Look our MTA delivers X number of messages per
> second on the same hardware theirs delivers X / 10 messages". We want to
> encourage this, but still support the slower expected behaviour.
MTA writers expect reliability in the first place.
--
Matthias Andree
place. :-)
--
Matthias Andree
applein <[EMAIL PROTECTED]> writes:
> I'm have a system Debian/GNU Linux 2.2r2 I'm where search howto make
> move my partitions ext2 for reiserfs?
Backup, Reformat, Restore. There is no direct conversion.
--
Matthias Andree
your UPS
has a decent surge filter and is fast to ramp up the voltage should the
main supply fail or show brownouts, then the risk may be small enough.
--
Matthias Andree
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." - Benjamin Franklin
lement that.
Oops. (/me runs)
--
Matthias Andree
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin
Could you please only quote the relevant parts, particularly, would you
erase deeper nesting of quotes in your replies? That'd help a lot of
people transfer less data they can still easily get from their own
mailer at a keypress. Thanks a lot.
On Tue, 25 Sep 2001, Jorge Nerín wrote:
> Who says t
a PACKET
interface. Not sure about the actual ATA 3, 4, or 5 standards.
Why are disk drives slower with their caches disabled on LINEAR writes?
--
Matthias Andree
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." - Benjamin Franklin
On Mon, 24 Sep 2001, Dieter Nützel wrote:
[fast write cache]
> Do you know of a Linux SCSI tool to enable it for testing purposes?
scsiinfo and scsi-config should do. They shipped with my SuSE Linux 7.0
and have been available on SuSE systems for ages.
4, ATA 5? Do they have
the FLUSH CACHE command listed, possibly as mandatory? That might be
rather useful to use after in a "synchronous" write.
--
Matthias Andree
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." - Benjamin Franklin
data and filesystems in
> more risk by not using a write cache as with using it.
Utterly non-sense.
Linear writing as dd mostly does is BTW something which should never be
affected by write caches.
--
Matthias Andree
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." - Benjamin Franklin
n. I'd return it as broken the first day I figured
it did lazy write-back caching. No file system can be safe on such
disks.
--
Matthias Andree
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." - Benjamin Franklin
ive file systems
such as msdos, vfat, ntfs, freevxfs or whatever). This one is for the
distributors to fix.
Had they left MSDOS as a module, things would have worked out: 1. ext2
in the kernel 2. initrd loads reiserfs 3. actual root (reiserfs) is
mounted 4. only now, msdos.o becomes available.
--
Mat
or you
> to demand we just use minix and answer all the newbies that report
> defective floppies shipped by us.
In fact, I've yet to see a broken floppy shipped by SuSE. The worst
thing I came across was a CD of some 6.x version which the CD-ROM drive
read at 8x speed (and I didn't b
worst-case behavior in a malicious sense but I
simply cannot risk such nonsense on a 270 GB RAID5 if users have shared
work directories.)
--
Matthias Andree
that's reason enough for an administrator not to
install reiserfs 3.6. Sorry.
--
Matthias Andree
Mike Benoit wrote:
> I've been bitten by running out of inodes on several occasions, and by
> switching to ReiserFS it saved one company I worked for over $250,000
> because they didn't need to buy a totally new piece of software.
ext3fs's inode density is configurable, reiserfs's hash overflow c
On Tue, 25 Jul 2006, Denis Vlasenko wrote:
> I, on the contrary, want software to impose as few limits on me
> as possible.
As long as it's choosing some limit, I'll pick the one with fewer
surprises.
--
Matthias Andree
r for /tmp, but the file system will take many
months to mature after integration) and it will be "mkfs" time - so
reiser4 better be mature before we go that way if there's no way back
short of "amrecover", "restore" or "tar -x".
Smashing out most of the Cc:s in order not to bore people.
--
Matthias Andree
mate the average file
size and with it underestimate the number of inodes needed. But even
then, I'd be interested to know if that's a real problem for systems
such as ZFS.
--
Matthias Andree
with
> Solaris... I think linux should do the same...
I think reallocating inodes for UFS and/or ext2/ext3 is possible, even
online, but someone needs to write, debug and field-test the code to do
that - possibly based on Andreas Dilger's earlier ext2 online resizing
work.
--
Matthias Andree
t; or alternatively (to start that for already existing directories):
>
> e2fsck -fD /dev/hdXX
hat is not "alternatively", but "tune2fs first", then "e2fsck -fD"
(which can't happen on a RW-mounted FS and you should only try this on
your rootfs if y
d to files after in 2001 or 2002.)
> * JFS just always worked for me. Though I've never ever had a broken
> HDD where it (or it's tools) could have shown how well-done they
> were, so from a crash-recovery point of view, it's untested.
SUSE removed JFS support from their installation tool for "technical
reasons" they didn't specify in the release notes. Whatever.
> ext3 always worked well for me, so why should I abandon it?
Plus, it and its tools are maintained.
--
Matthias Andree
o I haven't. As long as they are commercial, it's not likely that I
> > will.
>
> Why?
I'm trying to shift my focus away from computer administration and
better file systems than old-style non-journalling, non-softupdates UFS
are available today and more will follow.
Cc: list weeded out.
--
Matthias Andree
rability guarantee?
3000/s doesn't look too much like you're doing synchronous I/O (else
figures around 70/s perhaps 100/s would be more adequate), and cache
exercise is rather irrelevant for databases that manage real (=valuable)
data...
--
Matthias Andree
doesn't apply to
"broken hardware" failures. You need backups with a few generations to
avoid massively losing data.
--
Matthias Andree
ttle about the on-disk ext2 layout, but
since block relocating is already in place for shrink support in the
offline resizer, some of the work appears to be done already.)
--
Matthias Andree
e
and lazily writing back.
sdparm --clear=WCE /dev/sda # please.
--
Matthias Andree
arameters,
> mkfs options, etc..)
I don't know Postmark, I did suggest to turn the write cache off. If
your systems uses hdparm -W0 /dev/sda instead, go ahead. But you're
right to collect and evaluate suggestions first if you don't want to run
a new benchmark every day :)
--
Matthias Andree
but nice background
fsck after a crash, which is however easy on the I/O as of recent FreeBSD
versions). Which was their main point against logging/journaling BTW,
but they are porting XFS as well to save those that need instant
complete recovery.
--
Matthias Andree
obtained from StorageReview.com's Performance Database.)
--
Matthias Andree
s SHA1) on its database pages, to detect
corruptions and writes that were supposed to be atomic but failed
(because you cannot write 4K or 16K atomically on a disk drive).
--
Matthias Andree
th this. If
they are reading the whole file anyways, they can easily compute strong
checksums as they go, and record them for later use, and check so many
percent of unchanged files every day to complain about corruptions.
--
Matthias Andree
On Tue, 01 Aug 2006, Hans Reiser wrote:
> You will want to try our compression plugin, it has an ecc for every 64k
What kind of forward error correction would that be, and how much and
what failure patterns can it correct? URL suffices.
--
Matthias Andree
at couldn't fix certain
bugs, too, so trying with the latest version of the respective tools is
a must.
--
Matthias Andree
in that
it does not scribble over memory it has not allocated?
--
Matthias Andree
create a new file doesn't belong on _my_ production
machines, which shall migrate away from reiserfs on the next suitable
occasion (such as upgrades). There's ext3fs, jfs, xfs, and in 2006 or
2007, we'll talk about reiser4 again. Yes, I am conservative WRT file
systems and storage.
--
Matthias Andree
ago and unloaded the
reiserfs kernel module, as the way how Hans has responded to the error
report is inacceptable.
Anyone is free to choose the file system, and as the simple
demonstration code posted earlier shows a serious flaw in reiserfs,
Hans's response was boldfaced, I ditched reiserfs3. End of story.
--
Matthias Andree
other filesystems?
I doubt new software is bug-free. I don't expect NFS problems with
reiser4 though, these should be in the regression tests. :-)
--
Matthias Andree
for the past five years" is not a proper response to
a real-world problem.
--
Matthias Andree
tch. Better by far to fix bugs in V4,
> which is pretty stable these days.
Better to fix a known bug than create a file system vacuum before V4 is
really stable.
Anyways, I don't care any more, I'm phasing out ReiserFS v3 and have no
plans to try V4 before 2006.
--
Matthias Andree
line reiser4 contract work before I can deal with that", fine, he
didn't but said "use reiser4 instead". And that's inadequate.
And I say this without any emotions, red head, swelling veins and such.
--
Matthias Andree
backups, plus
off-site archives, are probably a good idea for these circles then.
--
Matthias Andree
il someone talks about
implementing a whole versioning system for reiser4.
--
Matthias Andree
space got low
That isn't desired. See above.
> Well, it hasn't been coded solely because we haven't gotten around to it
> what with all else that needs doing and still needs doing. Remind me
> about this in a year.:)
Save this mail to a file and have atd mail it to you. Or use a calendar :)
--
Matthias Andree
77 matches
Mail list logo
