Displaying 4 results from an estimated 4 matches for "99mb".
Did you mean:
99m
2010 Aug 01
1
Are enormous extents harmful?
...'t possibly slow things down by more than 1%.
(And, that''s the worst-possible case.)
But, large extents (I think) also have costs. For instance, if you are
writing a byte into the middle of an extent, doesn''t Btrfs have to copy
the entire extent? If so, and if you have a 99MB extent, the cost
of that write operation will be *huge*.
Likewise, if you have compressed extents, and you want to read one
byte near the end of the extent, Btrfs needs to uncompress the
entire extent. Under some circumstances, you might have to
decompress 99MB to read one short block of data....
2003 Jul 18
2
pf
...s
############ SHAPING goes here ###############################
altq on $intif cbq bandwidth 100Mb queue {etherdown, downstream}
queue etherdown bandwidth 96% cbq(default)
queue downstream bandwidth 4% cbq
altq on $extif cbq bandwidth 100Mb queue { etherup, upstream}
queue etherup bandwidth 99Mb cbq(default)
queue upstream bandwidth 386Kb cbq
pass in quick on $intif from 172.16.0.0/16 to 172.16.0.0/16 queue etherdown
pass out quick on $intif from 172.16.0.0/16 to 172.16.0.0/16 queue etherup
pass in on $intif proto tcp from 172.16.0.0/16 to any port 80 keep state queue downstream
pass in...
2008 Feb 22
0
mddisk(ramdisk) root system that image size limit ?
...an 100MB of image (image for ramdisk, mfs root)
The loader.rc {
load kernel // The kernel used 6.2 GENERIC
load -t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=128k
}
above config can't boot normal, reboot immediately.
create a equal 100MB or equal 99MB of image (image for ramdisk, mfs root)
The loader.rc {
load kernel // The kernel used 6.2 GENERIC
load -t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=100k
(or count=99k)
}
above config can't boot normal, kernel panic.
[TEST after system up]
1....
2013 Nov 26
1
Bad size transfers
...her server that has an curlftp
mount of another server.
Most of the times, sync happens right, but in other opportunities, I see
by the logs that files are partially transferred and deleted from source
(as specified by the flag) but destination file is far from a copy of
the original. In example, a 99MB file was transferred, it copied 22MB
and then deleted the source without errors.
?Is there a way that rsync prints individual file transfer size instead
of a total at the end?
I have just set rsync to verbose at this time, but if requested, I can
make some tests with -vvv flag
Regards,