.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg07439/pgp0.pgp
Description: PGP signature
.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg07446/pgp0.pgp
Description: PGP signature
, you have *two*
constraints: (1) the job has to finish in under 9 hours, (2) It has to consume
few enough resources that nothing else bogs down
--
Valdis Kletnieks
Computer Systems Senior Engineer
not be asking.
You might want to look into whether Solaris 7, 8, or 9 address your
performance concerns - Solaris 6 is quite ancient.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
box?
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg06845/pgp0.pgp
Description: PGP signature
before shredding has a subtle hole in it - since you will unpack
into *different* disk blocks and then shred *those* blocks, you will be
leaving unshredded data in the blocks the file occupied before unpacking.
--
Valdis Kletnieks
Computer
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg06609/pgp0.pgp
Description: PGP signature
a tool like fsck makes me curl up like a
breaded prawn. ;)
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg06481/pgp0.pgp
Description: PGP signature
-style version
numbers on files.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg05584/pgp0.pgp
Description: PGP signature
fragments as actually needed. It's a big win - /usr (even with all the binaries)
needs about 30% less space, and I've seen over 50% for file systems with
source trees in them...
--
Valdis Kletnieks
Computer Systems Senior Engineer
a lazy copy) if someone writes to one of
them?
Something I'd like to see even more than that would be VMS-style version
numbers on files.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
...
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
reiserfs detect that I have two copies of
the same file on disk and store tham as one file
(doing a lazy copy) if someone writes to one of
them?
Something I'd like to see even more than that would be VMS-style version
numbers on files.
--
Valdis Kletnieks
% less space, and I've seen over 50% for file systems with
source trees in them...
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
that would be VMS-style version
numbers on files.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
- /usr (even with all the
binaries)
needs about 30% less space, and I've seen over 50% for file systems with
source trees in them...
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
of
them?
Something I'd like to see even more than that would be VMS-style version
numbers on files.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
of
the same file on disk and store tham as one file
(doing a lazy copy) if someone writes to one of
them?
Something I'd like to see even more than that would be VMS-style version
numbers on files.
--
Valdis Kletnieks
Computer Systems Senior Engineer
-compressing each 4K block and then only saving as many 512 byte
fragments as actually needed. It's a big win - /usr (even with all the
binaries)
needs about 30% less space, and I've seen over 50% for file systems with
source trees in them...
--
Valdis Kletnieks
.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
systems with
source trees in them...
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
to one of
them?
Something I'd like to see even more than that would be VMS-style version
numbers on files.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
On Sun, 19 May 2002 13:44:54 +0400, Oleg Drokin said:
Since usually you cannot reliable predict a crash time (note, that if you
can and it is SW fault, you should file a bug report instead, I think).
Wasn't there a Dilbert cartoon about a PHB that wanted advance announcement
of unscheduled
)
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg05263/pgp0.pgp
Description: PGP signature
, or what...
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg05199/pgp0.pgp
Description: PGP signature
with running
on a live mounted filesystem.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
msg05018/pgp0.pgp
Description: PGP signature
On Wed, 16 Jan 2002 15:22:45 GMT, toad [EMAIL PROTECTED] said:
Hi. Reiserfs packs small files well, and has problems with large tails.
So would it make sense to try to gzip tails before packing?
AIX already supports this sort of compression. Interestingly enough,
they use LZ compression
On Wed, 16 Jan 2002 19:22:58 GMT, toad said:
If you're cpu-bound, you probably don't want to compress anything,
unless a smaller tail is a lot easier to pack, which the reiserfs docs
seem to suggest... possibly this won't gain you enough to offset the
cost of compression though. Benchmarking
see if you can configure your iSCSI
to delay reporting a write as complete until it's actually committed to the
platters - that will close most of the race conditions (at the cost of
write performance).
--
Valdis Kletnieks
Operating
://people.redhat.com/alexl/files/fam_dnotify.patch
Hope this helps...
--
Valdis Kletnieks
Operating Systems Analyst
Virginia Tech
msg03826/pgp0.pgp
Description: PGP signature
On Mon, 07 Jan 2002 17:23:57 +0100, Russell Coker said:
disk geometry is usually not worth knowing and lied about by the hard
drive.
I suspect that this is usually the case on mainframes too. Valdis?
Well.. OK.. you caught me there. Older IBM disk drives *did* lie
about their geometry
these 3 patches works well) - is OK if that's not cutting edge.
2) The current seems to work, seems stable, please test list.
3) The current bleeding edge, test but expect problems list.
--
Valdis Kletnieks
Operating Systems Analyst
controller ratio gets a lot better with SCSI - but then you get to
re-calculate your break-even point because SCSI tends to cost more.
--
Valdis Kletnieks
Operating Systems Analyst
Virginia Tech
on??
I suspect Reiser doesn't update the inode count fields that 'df' looks at
because it's able to dynamically allocate more on the fly. This is a
left-over from file systems that had the number of inodes hard-coded at
mkfs time.
--
Valdis Kletnieks
101 - 135 of 135 matches
Mail list logo