Hello Garrett :-)
UnionFS works very well on Linux based embedded systems and its very
powerful :-) I dont know the mdmfs sorry :-) +1 for your ideas :-)
Best regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-current@freebsd
Dimitry Andric wrote:
> On 2012-12-07 13:59, Dimitry Andric wrote:
> > On 2012-12-06 18:12, Mark Atkinson wrote:
> >> Short backstory, I had recently upgraded my workstation to the latest
> >> current which included clang as default cc now.
> > ...
> >> qdbus under kde segfaults in malloc with a hu
Running fsck -t ufs -fy solved the issue!!
http://i47.tinypic.com/35m1qxk.jpg
How reliable is new UFS2-SU+J? Are there any journal verification routines
(I heard about some chcecks in the background). Will automatic fsck on boot
force full filesystem checks in any case (like filesystem related ke
On Fri, Dec 7, 2012 at 11:06 PM, CeDeROM wrote:
> Hello Ian :-)
>
> This is the problem - / is read only and /etc/resolv.conf already links to
> nonexistent file. This way I cannot modify its content nor link other file
> (i.e. /var/resolv.conf) to /etc/resolv.conf. Creating /var/resolv.conf does
TB --- 2012-12-08 06:10:01 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-08 06:10:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
Hello Ian :-)
This is the problem - / is read only and /etc/resolv.conf already links to
nonexistent file. This way I cannot modify its content nor link other file
(i.e. /var/resolv.conf) to /etc/resolv.conf. Creating /var/resolv.conf does
not help either.
I think /etc/resolv.conf should point to
dd if=root_part of=root_part took loong time but it did not help :-(
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "
Thanks Warren :-)
I noticed that Western Digital disks MUST be preformatted this way at
first otherwise stragne things happen later on (I had 3 disks like this for
desktop and laptop).
Best regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
On 12/07/12 17:20, Kevin Oberman wrote:
>
> ports/sysutils/smartmontools? Most modern disks support S.M.A.R.T and
> will log read or write errors as well as perform non-destructive
> (though far from comprehensive) testing.
This is the correct way, since the drive could be hiding bad blocks by
real
TB --- 2012-12-08 02:57:08 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-08 02:57:08 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-08 04:28:10 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-08 04:28:10 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-08 02:24:03 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-08 02:24:03 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Fri, 7 Dec 2012, Chuck Burns wrote:
dd if=/dev/zer of=/dev/ada0
^^^ There's your "badblocks" program. Any hard drive made in the last decade
have been self-remapping..
That should be /dev/zero. And this will be very slow, going one
512-byte block at a time. Using a 64K or 128K buffer
TB --- 2012-12-08 01:45:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-08 01:45:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-08 01:14:50 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-08 01:14:50 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
I don't believe the patch I just committed to head
for the kernel RPC to add backchannel support or
the NFS client patch coming soon should affect
operation unless the new "minorversion=1" is used.
However, since the patch is fairly large, I thought
I'd give everyone a "head up", in case it someho
TB --- 2012-12-07 23:47:25 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 23:47:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Fri, Dec 7, 2012 at 3:25 PM, Adam Vande More wrote:
> On Fri, Dec 7, 2012 at 5:05 PM, Tomek CEDRO wrote:
>
>> As I get ffs_valloc kernel panic on my / I want to check for badblocks but
>> cannot do that from the system itself so I need another FreeBSD instance to
>> run badblocks on unmounted
On Fri, 2012-12-07 at 23:34 +0100, Bas Smeelen wrote:
> On 12/07/12 23:11, Chuck Burns wrote:
> > On 12/7/2012 3:50 PM, CeDeROM wrote:
> >> Hello :-)
> >>
> >> I have tried to chceck for badblocks on my / but I did not find
> >> badblocks
> >> program on LiveCD and there is no option to install it
On Fri, Dec 7, 2012 at 5:05 PM, Tomek CEDRO wrote:
> As I get ffs_valloc kernel panic on my / I want to check for badblocks but
> cannot do that from the system itself so I need another FreeBSD instance to
> run badblocks on unmounted /. There are no badblocks on LiveCD and I cannot
> simply down
As I get ffs_valloc kernel panic on my / I want to check for badblocks but
cannot do that from the system itself so I need another FreeBSD instance to
run badblocks on unmounted /. There are no badblocks on LiveCD and I cannot
simply download it with pkg_add -r. Installing another system just to te
On Dec 7, 2012, at 2:39 PM, Devin Teske wrote:
>
> On Dec 7, 2012, at 2:30 PM, CeDeROM wrote:
>
>> Hello Chuck :-)
>>
>> DD cannot perform non-destructive test.. unless I do dd if=/dev/ada0s2a
>> of=/dev/ada0s2a :-) Do you think drives are now smart enough to remap
>> badblocks this way? What
On Dec 7, 2012, at 2:30 PM, CeDeROM wrote:
> Hello Chuck :-)
>
> DD cannot perform non-destructive test.. unless I do dd if=/dev/ada0s2a
> of=/dev/ada0s2a :-) Do you think drives are now smart enough to remap
> badblocks this way? What is the probability that there are no badblocks or
> badblock
On 12/07/12 23:11, Chuck Burns wrote:
On 12/7/2012 3:50 PM, CeDeROM wrote:
Hello :-)
I have tried to chceck for badblocks on my / but I did not find
badblocks
program on LiveCD and there is no option to install it. This is very
useful
utility, please add it as part of LiveCD :-)
Also there
Hello Chuck :-)
DD cannot perform non-destructive test.. unless I do dd if=/dev/ada0s2a
of=/dev/ada0s2a :-) Do you think drives are now smart enough to remap
badblocks this way? What is the probability that there are no badblocks or
badblocks are not detected this way?
Which pattern is better for
On 12/7/2012 3:50 PM, CeDeROM wrote:
Hello :-)
I have tried to chceck for badblocks on my / but I did not find badblocks
program on LiveCD and there is no option to install it. This is very useful
utility, please add it as part of LiveCD :-)
Also there is a problem with DHCP based workstations
Hello :-)
I have tried to chceck for badblocks on my / but I did not find badblocks
program on LiveCD and there is no option to install it. This is very useful
utility, please add it as part of LiveCD :-)
Also there is a problem with DHCP based workstations using LiveCD -
although interface gets
On 12/7/2012 12:31 PM, CeDeROM wrote:
Hello :-)
After days of problem with my system storage (?) I think I have located the
issue, or at least I am able to reproduce it, please take a look at
attached picture (photo of a crash).
At first I thought that was the Ext2 filesystem issue, but then I
On 12/07/12 19:32, Garrett Cooper wrote:
> On Fri, Dec 7, 2012 at 6:56 AM, O. Hartmann
> wrote:
>> After bind9 commits, building FreeBSD 10.0-CURRENT #0 r243946: Thu Dec
>> 6 12:18:13 CET 2012 refuses to work with the below error.
>
> Erwin's aware of the breakage (see the svn commit thread
On Fri, Dec 7, 2012 at 6:56 AM, O. Hartmann wrote:
> After bind9 commits, building FreeBSD 10.0-CURRENT #0 r243946: Thu Dec
> 6 12:18:13 CET 2012 refuses to work with the below error.
Erwin's aware of the breakage (see the svn commit thread for r243981).
Thanks,
-Garrett
_
Hello :-)
After days of problem with my system storage (?) I think I have located the
issue, or at least I am able to reproduce it, please take a look at
attached picture (photo of a crash).
At first I thought that was the Ext2 filesystem issue, but then I have
replaced the filesystem to UFS2-SU+
On 2012-12-07 17:43, Mark Atkinson wrote:
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
...
With this patch (placed in /usr/ports/devel/dbus-qt4/files), qdbus
starts up and exits normally for me. I did not do any other rigorous
testing, though. :)
Thanks for the awesome analysis. I will endea
TB --- 2012-12-07 15:10:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 15:10:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-07 15:10:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 15:10:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-07 15:10:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 15:10:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
> On 2012-12-07 13:59, Dimitry Andric wrote:
>> On 2012-12-06 18:12, Mark Atkinson wrote:
>>> Short backstory, I had recently upgraded my workstation to the latest
>>> current which included clang as default cc now.
>> ...
>>> qdbus under kde segfaults
TB --- 2012-12-07 15:45:59 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 15:45:59 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-07 15:10:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 15:10:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Fri, Dec 7, 2012 at 4:09 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
> In short - if you choose Gjournal with data and journal on the same disk,
> you will have about half write speed.
Okay, minus for GJournal in that case, but it is very interesting
solution, as most of the stuff in FreeBSD
CeDeROM wrote:
On Fri, Dec 7, 2012 at 2:41 PM, Ivan Voras wrote:
It looks like you are confusing GEOM journalling (-J) and UFS-SU
journalling (-j). They are very different, and today you probably want
to use the latter. If you are installing 9.x from scratch, it will be
enabled by default. If n
TB --- 2012-12-07 14:31:57 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 14:31:57 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
After bind9 commits, building FreeBSD 10.0-CURRENT #0 r243946: Thu Dec
6 12:18:13 CET 2012 refuses to work with the below error.
Regards,
Oliver
[...]
cc -O3 -pipe -fno-strict-aliasing -march=native -march=native
-DVERSION='"9.8.4-P1"' -DHAVE_CONFIG_H -D_REENTRANT -D_THREAD_SAFE
-DLIBINTERFACE=
TB --- 2012-12-07 14:06:14 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 14:06:14 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-07 13:44:02 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-07 13:44:02 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Fri, Dec 7, 2012 at 2:41 PM, Ivan Voras wrote:
> It looks like you are confusing GEOM journalling (-J) and UFS-SU
> journalling (-j). They are very different, and today you probably want
> to use the latter. If you are installing 9.x from scratch, it will be
> enabled by default. If not, you ca
On 2012-12-07 13:59, Dimitry Andric wrote:
On 2012-12-06 18:12, Mark Atkinson wrote:
Short backstory, I had recently upgraded my workstation to the latest
current which included clang as default cc now.
...
qdbus under kde segfaults in malloc with a huge recursion stack:
...
This is a bug in
On 07/12/2012 14:52, CeDeROM wrote:
> On Fri, Dec 7, 2012 at 2:41 PM, Ivan Voras wrote:
>> It looks like you are confusing GEOM journalling (-J) and UFS-SU
>> journalling (-j). They are very different, and today you probably want
>> to use the latter. If you are installing 9.x from scratch, it wil
On Fri, Dec 7, 2012 at 2:41 PM, Ivan Voras wrote:
> It looks like you are confusing GEOM journalling (-J) and UFS-SU
> journalling (-j). They are very different, and today you probably want
> to use the latter. If you are installing 9.x from scratch, it will be
> enabled by default. If not, you ca
On 07/12/2012 09:44, CeDeROM wrote:
> Any hints welcome :-)
It looks like you are confusing GEOM journalling (-J) and UFS-SU
journalling (-j). They are very different, and today you probably want
to use the latter. If you are installing 9.x from scratch, it will be
enabled by default. If not, you
On 2012-12-06 18:12, Mark Atkinson wrote:
Short backstory, I had recently upgraded my workstation to the latest
current which included clang as default cc now.
...
qdbus under kde segfaults in malloc with a huge recursion stack:
[...]
#44740 0x282f7bd4 in QObject::QObject () from
/usr/local/li
Hello,
I wrote a small patch for /etc/network.subr to add support for
ipv6_addrs_IF aliases in rc.conf(5) to match the already existing
ipv4_addrs_IF aliases for ipv4 addresses. With this patch the ipv6
aliases can be written like:
ipv6_addrs_re0="2001:db8::::1/64 2001:db8::::2/64
Hello,
thank you for your answer.
Unfortunately, I'm unexperienced with FreeBSD, and am absolutely unfamiliar
with hardware specifics. During this mail conversion, I have heard abour BAR
for the first time, and therefore, I know neither what exactly I should do
(e.g. how I can find the start o
Hello :-)
I am new to journaled UFS2, so there goes some questions and remarks:
1. GJournal MUST be run before NewFS, especially on one provider, this
should be clearly stated in NewFS manual, before hotshots like me first
create the fs and then want the journal, please update.
2. Is it possible
53 matches
Mail list logo
