I've seen some stuff online that made it look like using hard-link trees
and then doing some rsync worked, but some of this appears to be obsoleted
by new rsync features. If anyone has a pointer, that would be much
appreciated.
Thanks,
-Clint
--
This message has been scanned for viruses and
da
I'm seeing this sometimes before my machine dies:
Oct 26 03:28:00 belle kernel: acd0: WARNING - READ_TOC taskqueue timeout -
completing request directly
Oct 26 03:28:00 belle kernel: acd0: WARNING - READ_TOC freeing taskqueue zombie
request
Oct 26 03:30:00 belle kernel: acd0: WARNING - READ_TOC
On Oct 08, Kevin Oberman wrote:
> I had a system that was showing these exact symptoms David described. It
> did this both with -L and without. I went for about 3 months without a
> successful dump. I did at least two full system re-installs to no avail.
> Then, about 3 weeks ago, when I was about
This is all /really/ helpful:
mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Resource temporarily
unavailable
dump: Cannot create /home/.snap/dump_snapshot: No such file or directory
>From /var/log/messages:
fsync: giving up on dirty
0xc524b330: tag devfs, type VCHR
usecount 1, writec
On Sep 21, Jeremy Chadwick wrote:
> The tool is behaving how it should. Try using the -a flag.
Ok, I feel dumb now :)
Thanks,
-Clint
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
On Sep 21, Jeremy Chadwick wrote:
> With regards to this specific item: can you provide the full smartctl
> command you're using (including device), and all of the output? I have
> an idea of what the problem is, but I'd need to see the output first.
# smartctl /dev/ad6
smartctl version 5.38 [i38
On Sep 21, Jeremy Chadwick wrote:
> You could also consider using clri(8) to clear the inode (190). Do this
> in single-user while the filesystem is not mounted. After using clri,
> run fsck a couple times.
Booting single-user and running fsck again seems to have corrected these
errors. For som
On Sep 21, Jeremy Chadwick wrote:
> Re-adding mailing list to the CC list.
>
> No, I don't think that is the case, assuming the filesystems are UFS2
> and are using softupdates. When booting multi-user, fsck is run in the
> background, meaning the system is fully up + usable even before the fsck
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY;
RUN fsck MANUALLY.
Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix
whatever to the questions posed as fsck runs. What does this all mean?
On Sep 16, Jeremy Chadwick wrote:
> That's very strange then. Something definitely tried to utilise acd0 at
> that hour of the night. What is acd0 connected to, ATA-wise? Again, I
> assume it's PATA, but I'd like to know the primary/secondary and
> master/slave organisation, since you are using
On Sep 16, Mike Tancsa wrote:
> Would not bad cables (or trays) be consistent with symptoms like that ?
> i.e. the OS sees errors, but when we ask the drive, it says, "what
> errors". I am sure there are other things that could cause this, but in
> the past I would start with the cables and or tra
Hi Jeremy:
Thanks for your detailed response. Here are the answers I have thus far:
On Sep 16, Jeremy Chadwick wrote:
> acd0 is a CD/DVD drive. ad4 is a hard disk. What exactly were you
> doing with the system at the time these errors appeared? Were you using
> the CD/DVD drive? Was there a
Ok, I've had some flakiness with my 6.3-STABLE (Sun May 25 21:55:57 PDT
2008) box. I assume that these errors are indicative of a system-level
problem rather than a single disk:
Event 1
---
Sep 14 05:12:54 belle kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left)
LBA=216477719
Result: H
Hi:
Since upgrading from 5.4-STABLE to 6.2-RELEASE and now 6.3-STABLE, I've
noticed that occasionally sk0 goes weird. I don't quite get it. I was
able to connect to it via my local network, but routes to my WAN were
completely hosed. So, the machine becomes unable to ping or contact
anything th
On Nov 11, Chris H. wrote:
> It's as simple as making your swap slice available for dumping, and
> adding a line in your rc.conf file. Of course you'll need to "lift" the
> information of interest from the vmcore, for the dump to be of any value.
> :)
>
> http://www.freebsd.org/doc/en_US.ISO8859-1
On Nov 11, Dimitry Andric wrote:
> Any chance you could post some of these error messages? And if possible,
> backtraces, etc?
The messages amounted to page fault while in kernel mode or similar. The
problem is the system attempts to reboot itself within 15 seconds. I know
there is a way to pos
On Nov 11, [LoN]Kamikaze wrote:
> That's strange, I've gone right from 5.3 through to RELENG_7 without ever
> doing the reboots during the install process (I know that's not
> recommended) and I never ran into trouble. Did you accidently turn off
> compat6x in the kernel before you built? Did your
On Nov 02, [LoN]Kamikaze wrote:
> I think you might have no choice but to omit the reboots, because the
> world contains lots of stuff that has to do with the kernel (like
> mounting).
>
> So just go into single user mode and do the usual stuff:
> # make installkernel
> # mergemaster -p
> # make i
On Nov 04, Robert Watson wrote:
> When I upgrade a remote systems, I'll actually almost always run a few
> days with the new kernel and the old user space to make sure everything
> has settled nicely before doing the user space upgrade, which is harder
> to revert. Reverting to an old kernel is eas
On Nov 02, LI Xin wrote:
> So we get:
>
> - 5.5-STABLE works well on your box
> - 6.2-RELEASE stock GENERIC works fine
> - 6.3-PRERELEASE failed for some reason.
>
> So far as I am aware I have no clue why this could happen. Could you
> check if you have any special configuration in your /etc
I just attempted a source upgrade from 5.5-STABLE to 6.3-PRERELEASE, and it
was a disaster, more than likely because I forgot to do something.
Normally I'm saved by the fact that the operations are not so scary as to
cause problems.
Well, in this case after running 'make installkernel' and rebooti
Hi:
I bet this is documented /somewhere/, so if the response is in the form
of a single URL, I'm cool with that. I'm trying to buildkernel and I'm
getting config(8) errors:
ERROR: version of config(8) does not match kernel!
config version = 500013, version required = 63
What's the process o
get around the '...' argument with #define and
> deal with the extra argument.
Only C99 allows macros with variable arguments. But you can attempt to
just replace the function identifier (name) if the function's a
On Jun 06, Eduardo Meyer wrote:
> I need to know which files under /var a proccess (httpd here) is
> acessing. It is not logs because I have a different partition for
> logs.
>
> gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in
> fact with fstat I can see a number of httpd pro
On Mar 28, Pyun YongHyeon wrote:
> and sparc64(SMP) and I never see above errors. The only issue known to
> me is occasional watchdog timeout error which I really want to fix. But
> the watchdog timeout error is hard to reproduce and I couldn't reproduce
> the error on my system.
I'm still seeing
On Mar 26, Remo Lacho wrote:
> dump and restore are your friends.
>
> Try something like this for each new slice (partition):
>
> Create your new slice on the new disk.
>
> newfs the new slice - newfs -U /dev/[new_slice]
>
> mount the new slices - mount /dev/[new_slice] /mnt
>
> dump and res
26 matches
Mail list logo
