Am 08.05.2017 um 17:42 schrieb HSR Hackspace:
> Hi folks;
>
> I'm trying to format a 300 GB partition on x86_64 box running running
> BSD 10.1 with HW RAID configuration. All my attempt so far have
> failed. Below are the logs for same.
>
> Logs:
>
> 1. pod1208-wsa07:rtestuser 106] ./mkfs.ext3 /d
iliar with automating this, not
familiar with poudriere, and it requires a bit of work to get your
options transferred to these build systems. Such a "build all packages
first before you start deinstalling" would reduce the downtime, though.
Hope that helps a little.
Best regards
Matthias A
Am 23.04.2013 09:44, schrieb Alexander Motin:
> Let me disagree. bootverbose keeps dmesg readable for average user,
> while quirks are specific driver workarounds and their names may confuse
> more then really help. If every driver print its quirks, dmesg would be
> two times bigger. There is boot
Am 20.04.2013 23:29, schrieb Jeremy Chadwick:
>> My feeling is that the stalls are mostly from the error handler and the
>> overall time the drive is "frozen" gets shorter. If it had not _felt_
>> faster, I'd not have left that in sysctl.conf in the first place.
>
> Your understanding of what tha
Am 04.04.2013 03:05, schrieb Jeremy Chadwick:
>>> Please provide "gpart show -p ada1" output, both here and in the PR,
>>> if you could.
>>
>> =>63 1953525105ada1 MBR (931G)
>> 63 209714337 ada1s1 freebsd [active] (100G)
>>209714400 800 - free -
Am 04.04.2013 01:38, schrieb Jeremy Chadwick:
...
> While skimming Linux libata code and commits in the past, the only
> glaringly obvious bug/issue I see is with SB600/SB700 chipsets (the
> hardware revision apparently matters) and port multiplier (PMP) support
> and soft resets.
>
> Are you us
I have just sent more information to the PR at
http://www.freebsd.org/cgi/query-pr.cgi?pr=157397
The short summary (more info in the PR) is:
- limiting tags to 31 does not help
- disabling NCQ appears to help in initial testing, but warrants more
testing
- error happens during WRITE_FPDMA_QUEUE
Am 01.04.2013 17:07, schrieb Stefan Esser:
> Am 01.04.2013 15:14, schrieb Victor Balada Diaz:
>> Being able to configure quirks from loader.conf for disks AND controllers
>> would be great
>> and is not hard to do. If you want i can do a patch in two weeks and send it
>> to you. That
>> way it's
Am 31.03.2013 23:02, schrieb Scott Long:
> So what I hear you and Matthias saying, I believe, is that it should be
> easier to
> force disks to fall back to non-NCQ mode, and/or have a more responsive
> black-list for problematic controllers. Would this help the situation? It's
> hard to
> jus
Am 31.03.2013 06:00, schrieb Peter Wemm:
> We're talking about 10.x, so if you want it fixed, you need update
> with 10.x information.
>
> Please put 10.x diagnostics in the PR.
I will not. The PR was filed four months before 10-CURRENT branched;
I have no reason to assume it were to be no long
Am 28.03.2013 16:31, schrieb Scott Long:
>
> On Mar 28, 2013, at 8:00 AM, Ian Lepore wrote:
>
>> On Thu, 2013-03-28 at 09:17 +0200, Alexander Motin wrote:
>>> On 28.03.2013 02:43, Adrian Chadd wrote:
My main concern with the new stuff is that it requires CAM and that's
reasonably big c
Am 27.03.2013 22:22, schrieb Alexander Motin:
> Hi.
>
> Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
> stack, using only some controller drivers of old ata(4) by having
> `options ATA_CAM` enabled in all kernels by default. I have a wish to
> drop non-ATA_CAM ata(4) code,
Am 19.02.2013 19:54, schrieb Mikhail T.:
> These were, indeed, complaints, but not about the port "not working
> after I broke it". My complaint is that, though the port "works" out of
> the box, the office@ maintainers have given up on the base compiler too
> easily -- comments in the makefile ma
Am 03.01.2013 23:15, schrieb Mark Andrews:
> In message <50e5a7d1.4080...@freebsd.org>, Matthias Andree writes:
>> Am 03.01.2013 16:36, schrieb Eitan Adler:
>>> On 3 January 2013 02:32, Matthias Andree wrote:
>>>> Please do not quote addresses. Not all we
Am 03.01.2013 16:36, schrieb Eitan Adler:
> On 3 January 2013 02:32, Matthias Andree wrote:
>> Please do not quote addresses. Not all web archives and copies hide
>> them properly.
>
> Hiding email addresses is useless for spam control. Obfuscating them
> mak
Am 03.01.2013 01:50, schrieb Erich Dollansky:
> Hi,
>
> On Wed, 02 Jan 2013 17:02:11 +0100
> Matthias Andree <...@FreeBSD.org> wrote:
Please do not quote addresses. Not all web archives and copies hide
them properly.
>> The migration was made in order to g
Am 02.01.2013 06:31, schrieb Erich Dollansky:
> Hi,
>
>> Thank God! I'd hate to think that after unwinding years accumulated
>> CVS process, to rewind it for SVN, only to have to do it again for
>> GIT, just seems a bit masochistic.
>
> do not worry. It will come.
>
> Seriously, I do not underst
Am 31.12.2012 21:40, schrieb Chris H:
> IM(NS)HO; SVN is an inferior RCS created so Windows users wouldn't feel
> left out.
No, and it has nothing to do with Windows. CVS does work on Windows.
SVN 1.5 or newer is CVS done right, if you want the server-client split
model, and can waive the "dist
Am 20.08.2011 19:34, schrieb Dan Langille:
> This is an older system. I suspect insufficient ventilation. I'll look at
> getting
> a new case fan, if not some HDD fans.
The answer is quite simple, get new drives.
They have gone for some 24000 hours, IOW, at least 3 years (assuming
24x7), and a
Am 08.06.2011 19:59, schrieb Rob Farmer:
> Also, I've seen the sysctl kern.geom.debugflags=16 thing in zfs
> tutorials and such, but haven't seen where it's actually necessary. I
> think this is outdated and changed circa 8.0.
Possibly - it's still a de-facto standard reflex action whenever a new
Am 08.06.2011 15:11, schrieb nickolas...@gmail.com:
> 1. Change your root fstab record to /dev/ada0s4a (not label!), reboot
> to single mode and try to re-label partition.
Indeed not mounting from the label was (apparently) the key to solve
this. Thank you.
In fact the successful procedure was:
Greetings,
I've tried to re-label an existing (and up to date) 8-STABLE
installation's root partition. This failed, tunefs reports it cannot
write the super block.
I have attempted this sequence:
1. reboot (through BIOS and loader) directly into single-user mode
(boot -s)
2. sysctl kern.geom.de
s trying block 3, it should seek to 4704; OTOH if
anywhere block sizes get out of synch, that might explain it. Perhaps
truss can help if its output doesn't get scratched in the panic.
The interesting question is, which devices are affected,
Am 06.05.2011 20:37, schrieb Michael Hoffmann:
> I cannot reconstruct why 'pkgdb -Fu' did not tried to prevent me from
> using 'archivers/xz' furthermore, allthough it now seems to be marked as
> IGNORE. I also don't know how this LD_LIBRARY thing ever popped up in
> csh.cshrc, but it seems to
Am 05.04.2011 15:51, schrieb Andriy Gapon:
> Boris,
> ARC is an adaptive cache (as its name says), but the adaption doesn't happen
> instantly. So, when your applications do not use a lot of memory, but there
> is
> steady filesystem usage, then ZFS ARC is going to gradually grow to consume an
>
gcc command line, e.g.:
>
> echo "int main () { }" > t.c && gcc -v --help 2>&1 | grep m32 && gcc
> -m32 -B/usr/lib32 t.c
>
> Then it should work.
I experienced the same some time ago - but:
Shouldn't this (-B/usr/lib32) be subsumed under
ide pages, and possibly also from the FreeBSD ZFS manual pages.
HTH
Matthias
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
e me a much better performance on a 5400/min disk than I've ever had
with a halfway filled ZFS on the 7200/min RAID-class disk. And bulk
transfer rates of both drives are beyond any doubt.
In other words, the file system didn't recover speed (I'm not sure if
that's
Am 24.02.2011 12:44, schrieb Damien Fleuriot:
> Cheers, I've done just that :)
Merci.
I've just forwarded the PR to the maintainer for dis- or approval.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebs
Am 22.12.2010 14:53, schrieb Paul B Mahol:
> On 12/22/10, Jeremy Chadwick wrote:
>> On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote:
>>> Am 22.12.2010 13:44, schrieb Mike Tancsa:
>>> > On 12/22/2010 7:03 AM, Matthias Andree wrote:
>>> >&
Am 22.12.2010 14:29, schrieb Jeremy Chadwick:
> On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote:
>> Am 22.12.2010 13:44, schrieb Mike Tancsa:
>> > On 12/22/2010 7:03 AM, Matthias Andree wrote:
>> >> Greetings,
>> >>
>> >> I
Am 22.12.2010 13:44, schrieb Mike Tancsa:
> On 12/22/2010 7:03 AM, Matthias Andree wrote:
>> Greetings,
>>
>> I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs,
>> zfs,
>> vfs, or thereabouts have broken Tinderbox for me.
>&g
Greetings,
I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs, zfs,
vfs, or thereabouts have broken Tinderbox for me.
I'm mounting my ports tree via nullfs, which has been working fine for a year.
Any ideas, or further info needed?
Best regards
Matthias
__
Am 04.12.2010 15:24, schrieb Irakli:
> mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE
> -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq
> -I/usr/src/sys/i386/compile/NS /usr/src/sys/modules/ae/../../dev/ae/if_ae.c
> ===> aesni (depend)
> @ -> /usr/src/sys
> machine -> /usr/src/sys/i38
Am 01.09.2010 18:33, schrieb Jan Henrik Sylvester:
> I have got problems with GSSAPI authentication to OpenLDAP:
> ldap_sasl_interactive_bind_s: Other (e.g., implementation specific)
> error (80)
> additional info: SASL(-1): generic failure: GSSAPI Error: No
> credentials were supplied,
7; will have good reasons for it.
May have been RFC0974, perhaps in connection with others - January 1986...
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
ut no others?
I'm wondering if the etcmerge stuff should just ignore conflicts on the
$FreeBSD$ line.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send a
in advance!
Make sure that /proc is mounted, see the GNOME FAQ for details on how to
set /etc/fstab to make that happen automatically on boot.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
ck could have recovered quite a lot of such data (I can't tell, as I
didn't have full image backups).
Probably not fsck's fault, but if there is a major file system corruption,
it can wreak havoc.
--
Matthias Andree
___
freebsd-stable@f
Greetings,
could anybody have a look at bin/102299 please? The PR contains a patch to
fix malloc() differences between GNU libc and FreeBSD's libc, so this
should be little effort.
Thank you.
Best regards
--
Matthias Andree
___
freebsd-s
hen
upgrading from 7.1-R to 7.2-R.
Careful there - RELENG_7 is _newer_ than RELENG_7_2. The latter is
branched off RELENG_7 at some point and progresses much slower (as in:
errata and security, but no development), so that's no "update", but often
the
] were still empty when
I checked yesterday, and I find that makes it more difficult than
necessary to actually test the RC. Nevermind the schedule, and release
when it's done.
[1] http://www.freebsd.org/relnotes/7-STABLE/relnotes/new.html
--
Matthias A
main links point to empty documents, the snapshots
point to 7.0 release notes.
Particularly, can FreeBSD 7.2 support 256-byte inodes in ext2fs?
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Andriy Gapon schrieb:
> on 28/01/2009 21:22 Andrew Snow said the following:
>
>> Andriy Gapon wrote:
>>
>>> Previously I heard about problems with hardware running hot, but not
>>> with it being "cold". I put the word in quotes, because the system is in
>>> a room with normal room temperatu
Greetings,
I have a hard time with file system access.
Here's the story: I'd been unhappy about GEOM_JOURNAL within the same
provider as my /usr and /var partitions (used JOURNAL on a fresh
install), it would occasionally give up on fsync() for lock messups
(FreeBSD 7.1-RELEASE-p2). Several weeks
ke installworld" would be the easiest thing to do... but some
parts of the system use install -C (probably to avoid excessive
recompiling or relinking).
So what's the canonical way to "installworld" into a staging area so I
can just compare or rsync --del system direct
aps un-/reloading the kernel driver modules (if compiled as module)
is sufficient anyways -- the module will probably reprobe everything upon
reload; OTOH you can check usbd and devd and things if you can pin
devices to certain ordering.
--
Matthias Andree
_
re-plugged, right? At least my two
USB printers (easily told apart from the vendor ID) like to rearrange
their ordering frequently on Linux...
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e and next to
unusable; the Linux driver is flakey, the FreeBSD 6.1 driver however is
rock solid (but unusable, among other IEEE 802.11 stuff, under 6.0...)
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Wed, 09 Aug 2006, Nikolas Britton wrote:
> On 8/9/06, Matthias Andree <[EMAIL PROTECTED]> wrote:
> >
> >1. gzip isn't usually used to compress incompressible data.
> >
> >2. use "time" to figure out how much CPU time it actually burns.
> >
c options don't help with that, so
CPU time is better than wallclock time.
> gzip compiled with -O3:
> # date ; nice -10 ./gzip -c9 testfile > testfile.gz ; date
> Wed Aug 9 08:01:21 CDT 2006
--
Matthias Andree
___
freebsd-stabl
apaci` ap_cpystrn.c
> ...
>
> Note the -DHARD_SERVER_LIMIT=512 above.
Does it work if you type (you can omit the env in /bin/sh, bash, (pd)ksh
and other Bourne-like shells):
env APACHE_HARD_SERVER_LIMIT=1024 portinstall www/apache13
(Isn't it time to migrate to a newer Apache version
Alexander Skwar <[EMAIL PROTECTED]> writes:
> Good morning!
Ever thought that there might be more than Europe and Africa on the
lists?
> [...] Does FreeBSD support Linux LVM2?
No. You need a primary partition.
--
Matthias Andree
___
fr
to fail: you may try
attaching a syscall tracer such as truss, ktrace or strace (the latter
from ports) to the process and see if it leaks file descriptors. This
may fail due to permissions however.
--
Matthias Andree
___
freebsd-stable@freebsd.org ma
stem security fixes
are only provided for 4.10 and 4.11 at this time.
The ports tree has been requiring FreeBSD 4.8 at a minimum for a very
long time now, and I'd expect that even that it requires 4.11 soon
enough.
--
Matthias Andree
___
freebsd-sta
and maximum OSVERSION required" tags to packages to prevent
their being installed on incompatible systems.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nvolve ripping out the minimum
fix out of a larger patch set, it'll pretty much be a non-starter for me
unless someone funds that work.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
, 6.1 is a real and visible improvement over 6.0 for me.
6.1 is usable, where 6.0 toppled over every few minutes (I'm talking
about ral(4) and other nasty stuff such as tmpfs/mdmfs panics in 6.0 -
ral(4) is what prompted me to do the 5.4->6.0 upgrade).
--
Matthias Andree
_
so that particular bit is extremely hard to
find :-(
What is the brand and model of your so-called hardware RAID?
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Tenebrae <[EMAIL PROTECTED]> writes:
> On Sat, 1 Apr 2006, Matthias Andree wrote:
>
>> RAID1 is _not_ a backup, but an availability aid.
>> If going for RAID1, be sure to add a backup solution.
>
> More to think about...thank you.
> I am trying to get some peac
reasonable motherboards disk controller
>> is just as fast as any RAID controller.
>
> You can't boot off a system with a dead primary disk with software RAID1.
> (well you MIGHT but.. in any case RAID1 cards are quite cheap)
It's a matter of the BIOS:
wi
controller with battery backup unit (rare with SATA) and
use copyback (writeback) caching.
But don't ever dare use write caching without at least a dedicated UPS:
the corruption patterns of UFS with write caches on are extremely
destructive, been there, seen that -- with a test machine and only a
ds that work with 3.3 and 5 V, they have two of these
notches. See <http://www.digi.com/pdf/prd_msc_pcitech.pdf> for
discussion of voltages in PCI cards.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org
Holger Kipp <[EMAIL PROTECTED]> writes:
> It violates POLA on 5-STABLE, and it will violate POLA on 6-CURRENT,
> especially as most perl programmers assume /usr/bin/perl to be the
> correct path.
POLA doesn't apply to -CURRENT.
ume "#!/usr/bin/perl" works.
>=> removing a symlink to create lots_of_trouble(tm) is not the
> freebsd-ish way of live. this single symlink is needed.
The admin who wishes to have that symlink can place one himself. Why
burden the b
rm style is probably an infeasible task (recall 840 ports use
> /usr/bin/perl, and that's not counting the others that use another
> hardcoded variant of /usr/local/bin/perl).
Well, broken ports are marked broken and removed after some months.
How would broken Perl ports justify speci
on the first line of
> the script will work correctly.
As mentioned before, #! /usr/bin/env perl is the canonic SHORT way to
run perl, longer ways are in perlrun(1).
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd
y break after upgrading both perl and the port, they deserve no better.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Matthias Andree <[EMAIL PROTECTED]> writes:
> so apparently, three (checkouts.cvs:., . and ..) or four files (perhaps
> the # file) have disappeared. I'm not sure if fsck will revive them, I
> want to avoid destroying data useful for debugging.
OK, I dd'd the whole par
0
...
# camcontrol modepage da0 -m10
RLEC: 0
Queue Algorithm Modifier: 1
QErr: 0
DQue: 0
...
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ken Smith <[EMAIL PROTECTED]> writes:
> On Mon, Jan 17, 2005 at 10:28:53AM +0100, Matthias Andree wrote:
>
>> critical:
>> kern/60313 (silent data corruption on block devices)
>>still open, may be FreeBSD 4 specific after the GEOM flurry
>>
tarball, cd e2fsprogs-1.36rc2, then
proceed with mkdir build ; cd build ... as shown above.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[
>Submitter-Id: current-users
>Originator:Matthias Andree
>Organization:
>Confidential: no
>Synopsis: FreeBSD 4.11-RC3 GCC preprocessor failure
>Severity: critical
>Priority: high
>Category: gnu
>Class: sw-bug
>Releas
MFC sufficient) still open
> bin/46866 (false data from getpwent, easy to fix) still open
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
so
with patches attached remain unfixed in 4.11-RC3 when a reminder has
been sent after 4.11-RC1...
What this means for code quality is left to the reader's appreciation.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://list
46866 (false data from getpwent, easy to fix) still open
non-critical:
kern/44260 (missing device in LINT configuration)
is long-standing although trivial to fix (patch included)
--
Matthias Andree
___
freebsd-stable@freebsd.org
Matthias Andree <[EMAIL PROTECTED]> writes:
> OTOH, I am not convinced that fsck (particularly bgfsck) is bug-free,
> I
Make that "fsck and ufs are bug-free"...
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
ht
e than one.
That will limit the potential damage on the disk to one block rather
than the whole of the cache, which is between 2 and 8 MB on the common
drives sold today.
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ps MFC suffices)
kern/44260 LINT does not list pseudo-device tap
(trivial to fix)
--
Matthias Andree
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
code?
Likely. The same can be seen for CPUs, more and more specialization is
in the compiler. Ask Intel, Sun or Mips how much they're spending on
chip development and how much on compiler development. :)
--
Matthias Andree
___
[EMAIL PROTE
uary 2004 (on FreeBSD 4
though), see http://docs.freebsd.org/cgi/mid.cgi?m38yj15m59.fsf>
for the archived post, including logs.
So that makes two for me and some more for Dan.
--
Matthias Andree
___
[EMAIL PROTECTED] mailing list
http://lists.free
problem. May be a while while before I see the problem again, these
are very scarce fortunately (actually, the first SOFTDEP issue on this
machine at all).
OTOH, this is an IBM desktop drive in disguise, so the blatant firmware
errors should be known by now.
--
Matthias Andree
__
disk drive (Western Digital
Caviar AC420400D, a rebranded IBM DJNA drive)? I gather that ATA drives
are supposed to flush their caches on software (command) and hardware
resets (reset line active).
I did not power cycle.
--
Matthias Andree
___
[EMAIL
ssues in ports fixed, for
instance cups-base, open-motif, others? Yeah I know send patches, but my
ressources are limited and committers are also overworked already...
The general question I'd like to raise is how long will we allow ports
with known security flaws linger around before they ar
intainer for FreeBSD 4 perhaps?
Søren may not have the resources (time, interest, funds) of supporting
multiple trees at the same time -- however, leaving the bug open and
unassign it would have been the right thing to do.
--
Matthias Andree
Encrypted mail welcome
ually used on ServerWorks boards, are there hardware
detection/configuration issues in the kernel? Anything known?
Thanks in advance,
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
___
[EMAIL PROTECTED] mailing list
TS) if you want one, but they're around twice as expensive as
their flagship ATAPI CD writer.
I'm sure there are other good alternatives for either component (SCSI HA
and CD writer), but I can only talk about those I know first-hand.
--
Matthias Andree
Encrypt your mail: my GnuP
77), 32 MB PC66 + 64 MB PC100 RAM
(66 MHz FSB), nothing "server-class", but it seems to be fine even
under load with SuSE Linux 8.1 or 8.2 (dual-boot).
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
___
[EMAIL PR
ot;no such device".
Is this a known issue or should I file a PR?
TIA,
--
Matthias Andree
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
THEM CAREFULLY!)
--
Matthias Andree
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
arm, the Disk Fitness Test was able to repair the
> bad sectors without any major problems. Really good.
Nope. It hid the problems at the expense of spare sectors. Backup your
data and have the drive replaced. See the pertinent DTLA FAQs on the
web. These drives need special treatment.
--
Matthias Andree
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
d. I'm not entirely sure that it's NOT the board I/O timing, but
if it was, I'd shrug over why NT then worked.
However, if the changes are NOT to 4-STABLE, then I'm out. I cannot
migrate that machine to 5-CURRENT, in that case, testing would have to
wait until 5-STABLE.
l, and
I'm away from that machine). NT4 (it's a dual-boot machine) was fine.
Is this anything easily fixed?
Thanks,
--
Matthias Andree
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
"Brossin Pierrick" <[EMAIL PROTECTED]> writes:
> Under Linux it was easy to find it.. /proc
> Under FreeBSD I can't find it..
Reboot into Linux, look at the BogoMIPS, then boot FreeBSD :-)
Run real benchmarks if you want hard figures. BogoMIPS only calibrates
delay
all these objections do not help
the regression or displeasing users. And the latter is a Bad Thing®.
--
Matthias Andree
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
x 2.4 and 2.5 ATA sub systems have higher troughput on
sequential read than FreeBSD 4.6-RC ATA. Never looked for latency
through the file system (and cannot, as the Linux 2.4.19-pre BSD FFS
file system is hosed.)
(OTOH, FreeBSD 4.6-RC SCSI -- at least the aic stuff with an Adaptec
294
f disabled
altogether? Or will 4.6 ship with ata as it is today, with the risk that
it breaks some systems 4.5 ata did work on?
--
Matthias Andree
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
ly), but if the
implementation in the drive has changed, I'm interested to see what will
happen soon, as I expect more drives to support tagged queueing now that
it's been in the ATA drafts for some time.
--
Matthias Andree
"They that can give up essential liberty
d just not part of the system?
--
Matthias Andree
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
example?
Would opening a directory and fsync()ing flush all pending changes to
the directory and guarantee fsync() does not return before writes are
written (assuming write caches in the disk drive are switched off, of
course)?
--
Matthias Andree
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
1 - 100 of 102 matches
Mail list logo
