Dear All,
It looks like I'm able to recover all of the deleted files.
I'm using UFS Explorer Professional Recovery, I'm working on it for more than
30 hours, its a long time but it works!
Yaaay!
Laci
Sent from my mobile.
On 2013.09.09., at 0:36, kpn...@pobox.com wrote:
On Mon, Sep 09, 2013
On Tue, 10 Sep 2013 22:38:46 +0200, Laszlo Danielisz wrote:
Dear All,
It looks like I'm able to recover all of the deleted files.
I'm using UFS Explorer Professional Recovery, I'm working on it
for more than 30 hours, its a long time but it works!
If recovery works, time does not matter
I end up deleting the whole directory, of
course with precious informations.
I have ufs on the hdd, after the accident I've turned off the computer to
avoid any writings on the disk.
Do you have any idea how can I recover the lost directory?
Thank you!
Laci
anymore
and rsync had the --delete parameter I end up deleting the whole directory, of
course with precious informations.
I have ufs on the hdd, after the accident I've turned off the computer to
avoid any writings on the disk.
Do you have any idea how can I recover the lost directory?
Thank
parameter I end up deleting the whole
directory, of course with precious informations.
I have ufs on the hdd, after the accident I've turned off the computer to
avoid any writings on the disk.
Do you have any idea how can I recover the lost directory?
Thank you!
Laci
Hi Laci,
I'm
.
I had a little rsync script which I used to synchronise a directory
between those two hard drives, because one of the hard drives were
not present anymore and rsync had the --delete parameter I end up
deleting the whole directory, of course with precious informations.
I have ufs on the hdd
Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Laszlo Danielisz
Sent: 08 September 2013 09:47
To: FreeBSD Questions
Subject: ufs recovery
Hi,
By mistake I forgot to edit my crontab on my FreeBSD 8.3 after I took out one
of the hard
Of Laszlo Danielisz
Sent: 08 September 2013 09:47
To: FreeBSD Questions
Subject: ufs recovery
Hi,
By mistake I forgot to edit my crontab on my FreeBSD 8.3 after I took out one
of the hard drives.
I had a little rsync script which I used to synchronise a directory between
those two hard
will buy you service at a
company specialized in recovery. There is no guarantee they
will be successful.
2. time
You invest time in learning how UFS works. There are many
excellent articles (especially the authoritative one by
M. K. McKusick). You try out different tools (with different
scope
_before_
starting the rsync. I would suggest you do something similar in the future.
Just to be clear, was the information deleted from _both_ harddisks?
I have ufs on the hdd, after the accident I've turned off the computer to
avoid any writings on the disk. Do you have any idea how can I
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get an
unable to write superblock error. This is before mounting the drive
RW
Hi,
On Sun, 9 Sep 2012 17:47:43 -0700
Kevin Oberman kob6...@gmail.com wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get an
unable to write superblock error
On Sun, 9 Sep 2012, Warren Block wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get
the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get an
unable to write superblock error. This is before mounting the drive
RW, but it is, of course, mounted RO.
This worked in a VM when I tested it just now. Maybe running fsck on that
filesystem first will help.
Already
it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get an
unable to write superblock error. This is before mounting the drive
RW, but it is, of course, mounted RO.
This worked in a VM when I tested it just now. Maybe running fsck
root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get an
unable to write superblock error. This is before mounting the drive
RW, but it is, of course, mounted RO
On Thu, May 10, 2012 at 9:29 PM, Edward M eam1edw...@gmail.com wrote:
On 05/10/2012 03:45 PM, Alejandro Imass wrote:
Regarding Nemeth's I am undecided between the 4th (Unix Linux) or
the 3rd. Please advise.
i purchased the third edition because I took a look in the 4th the table
of
mount a slice.
Given the BSD terminology: A slice _has_ to contain partitions.
You cannot format a slice, you can only format partitions. A
formatted partition carries a UFS file system. (However, it's
possible to omit the slice, and partition the whole disk instead,
this is called dedicated
On Thu, May 10, 2012 at 06:29:05PM -0700, Edward M wrote:
On 05/10/2012 03:45 PM, Alejandro Imass wrote:
Regarding Nemeth's I am undecided between the 4th (Unix Linux) or
the 3rd. Please advise.
i purchased the third edition because I took a look in the 4th
the table of contents
On 05/11/2012 10:47 AM, Chad Perrin wrote:
Is there something else I should try to find in the index or table of
contents that would be in the third edition but not the fourth? Can you
give me some examples of the sorts of things you'd expect to find in the
table of contents that is lacking in
On 05/11/2012 12:11 PM, Edward M wrote:
So far I think I found a few that may make a difference. According
to the table of contents in the 4th edition in the chapter called
Booting and shuting down it
only shows entries for: red hat, HP-UX, AIX, SUSE,Ubuntu. However
in the third
On Fri, May 11, 2012 at 12:11:48PM -0700, Edward M wrote:
So far I think I found a few that may make a difference.
According to the table of contents in the 4th edition in the
chapter called Booting and shuting down it
only shows entries for: red hat, HP-UX, AIX, SUSE,Ubuntu. However
On 05/11/2012 05:18 PM, Chad Perrin wrote:
I appreciate the time you put into this.
It was no problem at all:-)
had fun comparing.
Now that I'm free and have more time I went over the 3rd edition
table of contents and found a few instances
that mentions FreeBSD. In chapter Adding
Hi,
Today I have got a panic under the following scenario:
* FreeBSD 9.0-RELEASE in VMWare ESXi virtualized host
* Very busy host (java compilers, NFS server, lot of UFS snapshots)
* apache web server
* pgsql and mysql databases
* GENERIC kernel
The panic happened after:
1- to umount a UFS
On Tue, May 1, 2012 at 1:58 AM, Robert Bonomi bon...@mail.r-bonomi.com wrote:
[...]
Reading _both_ of McKusick's Design of .. books, and the 'Unix System
Admininstration Handbook', by Nemeth, et al. is a good _start_.
I just bought the FreeBSD one only unless there is a reason I should
On 05/10/2012 03:45 PM, Alejandro Imass wrote:
Regarding Nemeth's I am undecided between the 4th (Unix Linux) or
the 3rd. Please advise.
i purchased the third edition because I took a look in the 4th the
table of contents
and it appears anything FreeBSD related was remove and
On Thu, May 3, 2012 at 1:14 PM, Alejandro Imass a...@p2ee.org wrote:
On Thu, May 3, 2012 at 9:35 AM, Robert Bonomi bon...@mail.r-bonomi.com
wrote:
[...]
One comment: for 'defensive' purposes it would be useful to break ad6 up
into two slices, putting 'basejail' in it's own slice. Then,
Hi,
On Wednesday 09 May 2012 18:57:06 Alejandro Imass wrote:
On Thu, May 3, 2012 at 1:14 PM, Alejandro Imass a...@p2ee.org wrote:
On Thu, May 3, 2012 at 9:35 AM, Robert Bonomi bon...@mail.r-bonomi.com
wrote:
[...]
One comment: for 'defensive' purposes it would be useful to break
On Wed, May 9, 2012 at 8:53 AM, Erich Dollansky
er...@alogreentechnologies.com wrote:
Hi,
On Wednesday 09 May 2012 18:57:06 Alejandro Imass wrote:
On Thu, May 3, 2012 at 1:14 PM, Alejandro Imass a...@p2ee.org wrote:
On Thu, May 3, 2012 at 9:35 AM, Robert Bonomi bon...@mail.r-bonomi.com
partitions.
You cannot format a slice, you can only format partitions. A
formatted partition carries a UFS file system. (However, it's
possible to omit the slice, and partition the whole disk instead,
this is called dedicated mode). A third method is formatting
the whole disk (the 'c' device
Hi,
On Wednesday 09 May 2012 20:30:37 Alejandro Imass wrote:
On Wed, May 9, 2012 at 8:53 AM, Erich Dollansky
er...@alogreentechnologies.com wrote:
Hi,
On Wednesday 09 May 2012 18:57:06 Alejandro Imass wrote:
On Thu, May 3, 2012 at 1:14 PM, Alejandro Imass a...@p2ee.org wrote:
On Thu,
above the chances of winning the
national lottery. But all of them ? Not a chance. He finally admitted that
he had very little knowledge about UFS and fsck, but still managed to do it
in a quite offensive way.
This is false. I have only been offensive, actually defensive, against
Robert Bonobi
, and 'fdescfs', and 'procfs' references removed, for clarity ]
/dev/ad6s1.journal on /usr/jails (ufs, asynchronous, local, gjournal)
/usr/jails/basejail on /usr/jails/yabarana-php53/basejail (nullfs,
local, read-only)
/usr/jails/basejail on /usr/jails/yabarana-php52/basejail (nullfs,
local, read-only
Alejandro Imass ait at p2ee.org writes:
...
devfs on /usr/jails/cmm-php52-1/dev (devfs, local, multilabel)
...
/usr/jails/basejail on /usr/jails/cmm-php52-1/basejail (nullfs, local,
read-only)
fdescfs on /usr/jails/cmm-php52-1/dev/fd (fdescfs)
procfs on /usr/jails/cmm-php52-1/proc (procfs,
/jails (ufs, asynchronous, local, gjournal)
/usr/jails/basejail on /usr/jails/yabarana-php53/basejail (nullfs,
[...]
Yes, that is a good start at useful detail. It is, presumably, _after_
the problem, and _after_ you had restored things to their proper places.
Yes.
Is it safe to assume
On Thu, May 3, 2012 at 12:05 PM, jb jb.1234a...@gmail.com wrote:
Alejandro Imass ait at p2ee.org writes:
...
devfs on /usr/jails/cmm-php52-1/dev (devfs, local, multilabel)
...
/usr/jails/basejail on /usr/jails/cmm-php52-1/basejail (nullfs, local,
read-only)
fdescfs on
Alejandro Imass ait at p2ee.org writes:
...
I have no idea, but cmm-php52-1 is in fact the problematic jail with
the MySQL problem.
Could you please include displays of
1. your troubled machine's
$ cat /etc/fstab
Note: you already showed us 'mount' output.
2. your other trouble-free
swapsw 0 0
/dev/ad4s1a / ufs rw 1 1
/dev/ad4s1d /tmpufs rw 2 2
/dev/ad4s1f /usrufs rw 2 2
/dev/ad4s1e /var
Alejandro Imass ait at p2ee.org writes:
...
OK. There is this anomaly in your troubled jail.
Because I have not been familiar with ezjail so I am learning it now as we go.
I will suggest to you some steps by intuition, and you have to judge for both
of us how to do it and what's appropriate.
Eitan Adler li...@eitanadler.com wrote:
On 30 April 2012 07:36, Robert Bonomi bon...@mail.r-bonomi.com wrote:
A competennt, not stupid, sysadmin would know these things. And not
'remove all doubt' (in the words of Abraham Lincoln), by raising such
nonsense questions.
A competent
On 04/30/2012 10:58 PM, Robert Bonomi wrote:
Reading_both_ of McKusick's Design of .. books, and the 'Unix System
Admininstration Handbook', by Nemeth, et al. is a good_start_.
Having a bunch of the books from O'Reilley Assoc. (http://www.ora.com),
especially for 'standard' tools that you
On 05/01/2012 06:43 AM, Polytropon wrote:
Except buying (good) books, you can also search for
articles on the web. For example, A Fast File System
for UNIX by M. K. McKusick is very interesting (at
least it was for me when I lost all my important data).
Some fs-related articles here:
On Tue, May 01, 2012 at 12:58:10AM -0500, Robert Bonomi wrote:
Reading _both_ of McKusick's Design of .. books, and the 'Unix System
Admininstration Handbook', by Nemeth, et al. is a good _start_.
Both? I'm aware of at least three (FreeBSD, 4.3BSD, and 4.4BSD) that
are probably within the
Hi,
On Tuesday 01 May 2012 20:43:43 Polytropon wrote:
On Tue, 01 May 2012 00:37:51 -0700, Edward M wrote:
On 04/30/2012 10:58 PM, Robert Bonomi wrote:
Reading_both_ of McKusick's Design of .. books, and the 'Unix System
Admininstration Handbook', by Nemeth, et al. is a good_start_.
-- it affects _only_
'file open' syscalls. fsck doesn't _touch_ nullfs.
Hint; journaling is an add-on to the UFS filesystem. nullfs doesn't know
what journaling is. Journal recovery doesn't _touch_ a nullfs.
A competennt, not stupid, sysadmin would know these things. And not
'remove all
Hi,
On Monday 30 April 2012 18:36:08 Robert Bonomi wrote:
Alejandro Imass a...@p2ee.org wrote:
That simply *ISN'T* going to happen -- not without a -lot- more evidence
than any individual can provide from a single =unrepeadable= incident.
ok, I am not the original poster but let me tell
On Mon, Apr 30, 2012 at 7:36 AM, Robert Bonomi bon...@mail.r-bonomi.com wrote:
Alejandro Imass a...@p2ee.org wrote:
On Sun, Apr 29, 2012 at 11:49 PM, Erich Dollansky wrote:
On Monday 30 April 2012 02:02:41 jb wrote:
Alejandro Imass ait at p2ee.org writes:
...
[...]
A competennt, not
On 04/30/2012 08:38 AM, Alejandro Imass wrote:
just not very helpful or fun. This attitude will get
He is helping,you need to learn how UFS, jails, nullfs,
journaling, disk I/O and other stuff work.
I have been following this thread and i must admit I also need to
learn more
On Mon, Apr 30, 2012 at 8:22 AM, Erich Dollansky
erichfreebsdl...@ovitrap.com wrote:
Hi,
On Monday 30 April 2012 18:36:08 Robert Bonomi wrote:
Alejandro Imass a...@p2ee.org wrote:
That simply *ISN'T* going to happen -- not without a -lot- more evidence
than any individual can provide from a
On Mon, Apr 30, 2012 at 1:03 PM, Edward M eam1edw...@gmail.com wrote:
On 04/30/2012 08:38 AM, Alejandro Imass wrote:
just not very helpful or fun. This attitude will get
He is helping,you need to learn how UFS, jails, nullfs, journaling, disk
I/O and other stuff work.
I have been
On 30 April 2012 07:36, Robert Bonomi bon...@mail.r-bonomi.com wrote:
A competennt, not stupid, sysadmin would know these things. And not
'remove all doubt' (in the words of Abraham Lincoln), by raising such
nonsense questions.
A competent sysadmin would ask questions when they don't know the
On Mon, Apr 30, 2012 at 1:23 PM, Eitan Adler li...@eitanadler.com wrote:
On 30 April 2012 07:36, Robert Bonomi bon...@mail.r-bonomi.com wrote:
A competennt, not stupid, sysadmin would know these things. And not
'remove all doubt' (in the words of Abraham Lincoln), by raising such
nonsense
On 04/30/2012 10:22 AM, Alejandro Imass wrote:
Oh, please! He's not helping anyone. He's just being an obnoxious
prick that thinks that by pointing out a lot of technical blabber and
some cheap philosophical posé
I guess i was going according to the fact that i have followed his
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/147420
that is about troubles with jails, nullfs, UFS, and NFS.
Synopsis: [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt inode)
Take a look at this paragraphs:
...
After two more failures, I now found the offending inode ...
...
As one
Quoth Eitan Adler on Monday, 30 April 2012:
On 30 April 2012 07:36, Robert Bonomi bon...@mail.r-bonomi.com wrote:
A competennt, not stupid, sysadmin would know these things. And not
'remove all doubt' (in the words of Abraham Lincoln), by raising such
nonsense questions.
A competent
://www.freebsd.org/cgi/query-pr.cgi?pr=kern/147420
that is about troubles with jails, nullfs, UFS, and NFS.
Synopsis: [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt inode)
Take a look at this paragraphs:
...
After two more failures, I now found the offending inode ...
...
As one point
Alejandro Imass ait at p2ee.org writes:
...
Thanks for pointing a plausible cause. What I have done so far is
limit the offending jail to a specific cpuset and I wanted to add
another disk to avoid contention with other jails. MySQL not only
consumes the whole CPUs but also limits the whole
me to post it anyway in addition to
your statement:
There is no problem in mentioning thoughts, possibilities
and options. It's also not a problem to admit a lack of
knowledge in certain fields (e. g. how UFS, journaling,
nullfs and fsck do interact with each other).
Things start to be problematic
the chances of winning the national lottery. But all of them ? Not a
chance. He finally admitted that he had very little knowledge about UFS
and fsck, but still managed to do it in a quite offensive way.
That was basically the point were I decided to stop to try to help him.
I think others felt
Hi,
On Monday 30 April 2012 22:38:13 Alejandro Imass wrote:
On Mon, Apr 30, 2012 at 7:36 AM, Robert Bonomi bon...@mail.r-bonomi.com
wrote:
A competennt, not stupid, sysadmin would know these things. And not
'remove all doubt' (in the words of Abraham Lincoln), by raising such
nonsense
On Sun, 29 Apr 2012 00:26:50 -0700, per...@pluto.rain.com wrote:
Alejandro Imass a...@p2ee.org wrote:
3) the directories were moved at reboot by journal recovery,
fsck or something else
I think it's *extremely* unlikely that fsck was involved, because
it just doesn't do things like
On Sun, Apr 29, 2012 at 4:37 AM, Polytropon free...@edvax.de wrote:
On Sun, 29 Apr 2012 00:26:50 -0700, per...@pluto.rain.com wrote:
Alejandro Imass a...@p2ee.org wrote:
3) the directories were moved at reboot by journal recovery,
fsck or something else
I think it's *extremely* unlikely
Alejandro Imass ait at p2ee.org writes:
...
And there was a log of a couple of ftp connections the same day this
happened, the ONLY 3 messages before the reboot at about 6 pm and they
were NOT from any of our customers. Here are the log entries:
Apr 27 05:54:37 nune ftp.proxy[2726]:
On Sun, Apr 29, 2012 at 1:15 PM, jb jb.1234a...@gmail.com wrote:
Alejandro Imass ait at p2ee.org writes:
...
And there was a log of a couple of ftp connections the same day this
happened, the ONLY 3 messages before the reboot at about 6 pm and they
were NOT from any of our customers. Here
Alejandro Imass ait at p2ee.org writes:
...
What you should do right now is to get some recent general or security
cd/dvd
with chkrootkit and rkhunter and run them from that external read-only
media.
I would also suggest that you look over config files of all packages
involved.
Hi,
On Monday 30 April 2012 02:02:41 jb wrote:
Alejandro Imass ait at p2ee.org writes:
...
What you should do right now is to get some recent general or security
cd/dvd
with chkrootkit and rkhunter and run them from that external read-only
media.
I would also suggest that
On Sun, Apr 29, 2012 at 11:49 PM, Erich Dollansky
er...@alogreentechnologies.com wrote:
Hi,
On Monday 30 April 2012 02:02:41 jb wrote:
Alejandro Imass ait at p2ee.org writes:
...
What you should do right now is to get some recent general or security
cd/dvd
with chkrootkit and
On Sat, Apr 28, 2012 at 1:43 AM, Wojciech Puchar
woj...@wojtek.tensor.gdynia.pl wrote:
All the jails wound up in the /usr/local/etc/apache22 of the only
surviving jail which is the http proxy to all the other jails.
Right before the server crashed I noticed MySQL at 100% o several CPUs
and
I somewhat agree, but it wasn't a person. I am the only administrator,
the only one with root access. The jails were effectively moved to the
/usr/local/etc/apache22 of the single that survived at the top level.
I'm thinking something between mount, EzJail, the journal and the way
MySQL created a
high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact. From what
I've learned so far, UFS is actually divided into 2 layers: one that
controls the directory structure and metadata and a lower layer
containing the data, so
a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact.
This is techically accurate, *BUT* the specifics of the quote corruption
unquote in the case under discussion
it yourself then it must be machine hardware problem
but still unlikely.
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact.
This is techically
DOES NOT ramdomly move directories. if you
are
sure you didn't move it yourself then it must be machine hardware problem
but still unlikely.
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
Alejandro Imass aim...@yabarana.com wrote:
On Sat, Apr 28, 2012 at 11:39 AM, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
Alejandro Imass aim...@yabarana.com wrote:
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have
it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact.
This is techically accurate, *BUT* the specifics of the quote corruption
unquote in the case under discussion make it *EXTREMELY
...@yabarana.com wrote:
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact.
This is techically accurate, *BUT* the specifics of the quote
, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
Alejandro Imass aim...@yabarana.com wrote:
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact
:
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact.
This is techically accurate, *BUT* the specifics of the quote corruption
unquote in the case under
On 04/28/2012 11:16 AM, Alejandro Imass wrote:
That is what worries me, is that it wasn't just some random bit or
cosmic ray, but the potential of happening again. I am not so sure
that it is*impossible* that a jail could affect other jails with
EzJail.
Sorry I'm late to the party. How
unlikely.
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact. From what
I've learned so far, UFS is actually divided into 2 layers: one that
controls
Alejandro Imass a...@p2ee.org wrote:
3) the directories were moved at reboot by journal recovery,
fsck or something else
I think it's *extremely* unlikely that fsck was involved, because
it just doesn't do things like that. It might move an orphaned
directory (or file) to lost+found, but
are
sure you didn't move it yourself then it must be machine hardware problem
but still unlikely.
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have somehow corrupted
the directory structure, whilst maintaining the data intact
On Sun, Apr 29, 2012 at 3:26 AM, per...@pluto.rain.com wrote:
Alejandro Imass a...@p2ee.org wrote:
[...]
Any chance that your base system -- rather than one of the jails --
has somehow been cracked; maybe even that the cracker precipitated
the crash? It might be wise to restore the whole
what you do FreeBSD DOES NOT ramdomly move directories. if you
are
sure you didn't move it yourself then it must be machine hardware problem
but still unlikely.
After a little more research, ___it it NOT unlikely at all___ that
under high distress and a hard boot, UFS could have
On Sat, Apr 28, 2012 at 10:20 PM, Erich Dollansky
erichfreebsdl...@ovitrap.com wrote:
Hi,
On Sunday 29 April 2012 08:58:17 Alejandro Imass wrote:
On Sat, Apr 28, 2012 at 5:03 PM, Erich Dollansky
er...@alogreentechnologies.com wrote:
[...]
Hi Erich, thanks for your reply.
I don't know
was UFS + Journal
Any help is GREATLY appreciated!
Thanks!
--
Alejandro Imass
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr
Imass
This is FreeBSD 8.2 updated, patched etc. The volume was UFS + Journal
Any help is GREATLY appreciated!
Thanks!
--
Alejandro Imass
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Hi,
On Saturday 28 April 2012 09:33:47 Alejandro Imass wrote:
On Fri, Apr 27, 2012 at 7:52 PM, Alejandro Imass aim...@yabarana.com wrote:
We had a server crash and required a hard reboot. The system is on one
disk and another disc mounts /usr/jails and everything runs in jails,
pristine
move here?
Anybody has ANY logical explanation???
Journaling is new to me. Could this be the cause?
Maybe so, I have no idea.
Maybe it's because EzJail mount volumes with each jail or some other
wild explanation. I honestly have never seen this before. I am just
glad that UFS was nice
something. I unmounted the drive and ran fsck and reported no
problems. df shows the data being use so where is the data??
your data is here as df shown usage and fsck see no errors. most probably
root directory of that volume got corrupted and subdirs were found and put
in lost+found
All the jails wound up in the /usr/local/etc/apache22 of the only
surviving jail which is the http proxy to all the other jails.
Right before the server crashed I noticed MySQL at 100% o several CPUs
and the server was on it's knees, so I'm wondering was this an
attack? is it possible that
Hi,
When booting my computer today I noticed the message at the end: starting
background filesystem check in 60 seconds. This seems strange to me since
SU+J is enabled on all filesystems. How is this possible? NB running
FreeBSD 9-STABLE
Regards,
Marco
--
In most instances, all an argument
On Mon, 30 Jan 2012 13:17:16 +0100 (CET)
Marco Beishuizen wrote:
Hi,
When booting my computer today I noticed the message at the end:
starting background filesystem check in 60 seconds. This seems
strange to me since SU+J is enabled on all filesystems. How is this
possible? NB running
Hello,
I've just updated my laptop from 8.2-RELEASE to 9.0-RELEASE, everything
worked but the kernel complains about labels see :
g_dev_taste: make_dev_p() failed (gp-name=vol/root, error=17)
g_dev_taste: make_dev_p() failed (gp-name=vol/root, error=17)
g_dev_taste: make_dev_p() failed
more now)
Block Sizes:
Maybe USB sticks may have different size/ speed front end
cache chips on USB sticks ? Hans would know I suppose. ?
Apart from soft updates, one can also choose the block sizes
newfs creates, I recall FFS is larger than UFS ?.
Maybe
Cheap USB drives, and even many CF drives, aren't much good as random
read-write devices. On my Soekris boxen I run FreeBSD, and mount the
root filesystem rw,noatime. And I don't write to it. ;-) /var is a
memory filesystem, there /var/db/... contain symbolic links to
/usr/local/db/.. because
El día Thursday, December 08, 2011 a las 10:10:36AM +0100, Hans Petter Selasky
escribió:
# fdisk -I da0
# fdisk -B da0
# bsdlabel -w da0s1 auto
# bsdlabel -B da0s1
# bsdlabel -e da0s1
# newfs /dev/da0s1a
# mount /dev/da0s1a /mnt
When I now bulk write a big file to the file
On Thursday 08 December 2011 07:37:12 Matthias Apitz wrote:
Hello,
I encounter the following problem with UFS file systems on USB keys,
i.e. the problem is not only with one key, but with all I have; the key
in question here is:
Dec 7 22:17:47 tinyCurrent kernel: umass0: Generic Mass
On Thursday 08 December 2011 10:19:43 Matthias Apitz wrote:
El día Thursday, December 08, 2011 a las 10:10:36AM +0100, Hans Petter
Selasky escribió:
# fdisk -I da0
# fdisk -B da0
# bsdlabel -w da0s1 auto
# bsdlabel -B da0s1
# bsdlabel -e da0s1
# newfs /dev/da0s1a
# mount
1 - 100 of 464 matches
Mail list logo
