On Thu, Jun 9, 2011 at 3:43 PM, Greg Bonett wrote:
> One question though, you say it's necessary that "appropriate
> disk blocks have not been reused by more recent transactions"
> Is it not possible for me to just read all the disk blocks looking for
> the filename and string it contained? How b
On Thu, 2011-06-09 at 14:57 -0700, Artem Belevich wrote:
On Thu, Jun 9, 2011 at 1:00 PM, Greg Bonett wrote:
> > Hi all,
> > I know this is a long shot, but I figure it's worth asking. Is there
> > anyway to recover a file from a zfs snapshot which was destroyed? I
know
> > the name of the file and
On Thu, Jun 9, 2011 at 1:00 PM, Greg Bonett wrote:
> Hi all,
> I know this is a long shot, but I figure it's worth asking. Is there
> anyway to recover a file from a zfs snapshot which was destroyed? I know
> the name of the file and a unique string that should be in it. The zfs
> pool is on geli
I just bought one of those chinese (apparently the same unit relabeled
and being sold by multiple companies) realtek RTL8187B wifi units. The
price is right.
The label name on this one is WiFySky 1500mW.
other than the fact that the case it is enclosed in is really cheesy,
there is a more im
i'm not sure which list this belongs to, so i'm posting to -hackers and
-stable.
i've noticed for a while now that during heavy activity (for instance
buildworld), that top will get these kvm_read errors when reading proc
mem entries.
i have included a screenshot of what happens during such even
Hi all,
I know this is a long shot, but I figure it's worth asking. Is there
anyway to recover a file from a zfs snapshot which was destroyed? I know
the name of the file and a unique string that should be in it. The zfs
pool is on geli devices so I can't dd the raw device and look for it.
Any sugg
On Thursday, June 09, 2011 11:28:20 am Guido Falsi wrote:
> Hi!
>
> I'm having a problem with BTX hanging on an HP 6005 Pro PC.
>
> I have filed a followup to an existing PR about this exact problem:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=151122
>
> All the information there looks corre
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
we managed to disable bge0, by inserting the following:
+ if (device_get_unit(dev) == 0)
+ return (ENXIO);
+
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Disable-probing-of-bge1-tp3961580p4473468.html
Sent from the freebsd-stable mailing list a
Hi!
I'm having a problem with BTX hanging on an HP 6005 Pro PC.
I have filed a followup to an existing PR about this exact problem:
http://www.freebsd.org/cgi/query-pr.cgi?pr=151122
All the information there looks correct and stands true.
I have tried performing some trivial debugging on btxld
I have a FreeBSD 8-STABLE system that's been running stably since I
last upgraded and rebooted on May 8. Yesterday, I updated /usr/src to
get ZFS v28 and also seem to have gotten rid of my nice, solid re0
network interface:
re0: port
0xb000-0xb0ff mem 0xea21-0xea210fff,0xea20-0xe
2011/6/8 Josh Carroll :
>>> That would mean the only time a
>>> person can use tunefs on a root filesystem is when they either do it
>>> manually during the FreeBSD installation (adding "-t" to the list of
>>> newfs flags in the filesystem creation UI), or if they boot off of some
>>> other medium
2011/6/8 Matthias Andree :
> 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.
>
>
13 matches
Mail list logo
