David Demelier wrote:
Hello there,
I'm writing because after a power failure I was unable to log in on my
FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some
files disappeared, including /etc/pwd.db. Thus I was unable to log in.
I've been able to regenerate the
Michael Powell wrote:
[snip]
The other box is my first foray into the land of GPT, along with SU+J. It
was sitting at the 'couldn't mount... Press return for /bin/sh' line.
There was an error indicating that replaying one or more journals had
failed. I was able to successfully fsck all the
On Mon, 14 Oct 2013 05:02:22 -0400
Michael Powell wrote:
David Demelier wrote:
Hello there,
I'm writing because after a power failure I was unable to log in on
my FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly
but some files disappeared, including /etc/pwd.db. Thus I
On 14.10.2013 14:39, RW wrote:
On Mon, 14 Oct 2013 05:02:22 -0400
Michael Powell wrote:
David Demelier wrote:
Hello there,
I'm writing because after a power failure I was unable to log in on
my FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly
but some files disappeared,
On Mon, Oct 14, 2013 at 6:34 PM, David Demelier
demelier.da...@gmail.com wrote:
Why? SU+J is enabled by default. Isn't the purpose of a journaled file
system to ensure that any bad shutdown will protect data?
On GNU/Linux, on Windows you will not require anything else to recover
your data.
On Mon, Oct 14, 2013 at 11:34 AM, David Demelier
demelier.da...@gmail.comwrote:
Why? SU+J is enabled by default. Isn't the purpose of a journaled file
system to ensure that any bad shutdown will protect data?
As already stated, those measures are to preserve fs integrity eg meta data
is in
On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More amvandem...@gmail.com wrote:
On Mon, Oct 14, 2013 at 11:34 AM, David Demelier
demelier.da...@gmail.comwrote:
Why? SU+J is enabled by default. Isn't the purpose of a journaled file
system to ensure that any bad shutdown will protect data?
As
On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM cede...@tlen.pl wrote:
Then why random files gets damaged as well even they are not
accessed/written on power loss? :-)
Prove they weren't.
--
Adam Vande More
___
freebsd-questions@freebsd.org mailing
On Mon, Oct 14, 2013 at 6:56 PM, Adam Vande More amvandem...@gmail.com wrote:
On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM cede...@tlen.pl wrote:
Then why random files gets damaged as well even they are not
accessed/written on power loss? :-)
Prove they weren't.
Hmm, maybe /etc/pwd.db as David
On 10/14/2013 12:50 PM, CeDeROM wrote:
On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More amvandem...@gmail.com wrote:
On Mon, Oct 14, 2013 at 11:34 AM, David Demelier
demelier.da...@gmail.comwrote:
Why? SU+J is enabled by default. Isn't the purpose of a journaled file
system to ensure that any
On Mon, Oct 14, 2013 at 7:09 PM, Brad Mettee bmet...@pchotshots.com wrote:
On 10/14/2013 12:50 PM, CeDeROM wrote:
Then why random files gets damaged as well even they are not
accessed/written on power loss? :-)
Random files can be affected because the sectors of the hard disk containing
the
On 10/14/2013 6:16 PM, CeDeROM wrote:
Isn't there Journal to prevent and reverse such damage?
Unlike other journaling filesystems, UFS+J only protects the metadata,
not the data itself - i.e. I think it ensures you won't have to run a
manual fsck, but just like plain old UFS files may be
On Mon, 14 Oct 2013 18:34:36 +0200
David Demelier wrote:
On 14.10.2013 14:39, RW wrote:
If you are having problems with data integrity you might try
gjournal or zfs instead.
Why? SU+J is enabled by default. Isn't the purpose of a journaled file
system to ensure that any bad shutdown
On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran br...@cran.org.uk wrote:
On 10/14/2013 6:16 PM, CeDeROM wrote:
Isn't there Journal to prevent and reverse such damage?
Unlike other journaling filesystems, UFS+J only protects the metadata, not
the data itself - i.e. I think it ensures you won't
On 10/14/2013 7:33 PM, CeDeROM wrote:
Thank you for explaining :-) So it looks that it would be sensible to
force filesystem check every n-th mount..? Or to do a filesystem check
after crash..? Are there any flags like that to mark filesystem
unclean and to force fsck after n-th mount? That
On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM cede...@tlen.pl wrote:
Thank you for explaining :-) So it looks that it would be sensible to
force filesystem check every n-th mount..?
Please explain the logic in which this helps anything.
Or to do a filesystem check
after crash..?
Already
On Mon, Oct 14, 2013 at 1:43 PM, Adam Vande More amvandem...@gmail.comwrote:
mount -o sync
should be
mount sync
--
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
On Oct 14, 2013, at 11:33 AM, CeDeROM cede...@tlen.pl wrote:
On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran br...@cran.org.uk wrote:
On 10/14/2013 6:16 PM, CeDeROM wrote:
Isn't there Journal to prevent and reverse such damage?
Unlike other journaling filesystems, UFS+J only protects the
Thank you all for good hints! This will come handy! :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
On Mon, 14 Oct 2013, Bruce Cran wrote:
On 10/14/2013 6:16 PM, CeDeROM wrote:
Isn't there Journal to prevent and reverse such damage?
Unlike other journaling filesystems, UFS+J only protects the metadata, not
the data itself - i.e. I think it ensures you won't have to run a manual
fsck,
On Mon, 14 Oct 2013 11:48:18 -0700
Charles Swiger wrote:
Yes. Without journalling, you'd normally perform the full
timeconsuming fsck in the foreground.
Journalling removes the need for the background fsck which only recovers
lost space.
With journalling, it should be
able to do a
Charles Swiger wrote:
[snip]
Yes. Without journalling, you'd normally perform the full timeconsuming
fsck
in the foreground. With journalling, it should be able to do a journal
replay to restore the filesystem to an OK state, but sometimes that
doesn't restore consistency, in which case
On Mon, 14 Oct 2013 11:48:18 -0700
Charles Swiger wrote:
fsck_y_enable=YES
One of the most annoying things about SU+J is that fsck asks if you
want to use the journal. So fsck -y wont do a proper check unless the
journal replay fails.
___
On 14.10.2013 20:08, RW wrote:
On Mon, 14 Oct 2013 18:34:36 +0200
David Demelier wrote:
On 14.10.2013 14:39, RW wrote:
If you are having problems with data integrity you might try
gjournal or zfs instead.
Why? SU+J is enabled by default. Isn't the purpose of a journaled file
system to
On 14.10.2013 18:47, Adam Vande More wrote:
There is no *warranty* as explicitly stated in
http://www.freebsd.org/copyright/freebsd-license.html
Aha, please don't play on words ;-). I think you understood I was
speaking about the filesystem state
not a lawyer issue.
On 14.10.2013 20:43, Adam Vande More wrote:
On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM cede...@tlen.pl
mailto:cede...@tlen.pl wrote:
Thank you for explaining :-) So it looks that it would be sensible to
force filesystem check every n-th mount..?
Please explain the logic in which
Hi--
On Oct 14, 2013, at 11:51 AM, Daniel Feenberg feenb...@nber.org wrote:
This discussion skirts the critical issue - are files that are not open for
writing endangered? No description of the uses of journaling can be
considered informative if it doesn't address that explicitly. As a naive
On Oct 14, 2013, at 12:41 PM, RW rwmailli...@googlemail.com wrote:
On Mon, 14 Oct 2013 11:48:18 -0700 Charles Swiger wrote:
Yes. Without journalling, you'd normally perform the full
timeconsuming fsck in the foreground.
Journalling removes the need for the background fsck which only
Hello there,
I'm writing because after a power failure I was unable to log in on my
FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some
files disappeared, including /etc/pwd.db. Thus I was unable to log in.
I've been able to regenerate the password database with a live cd but
On 13 Oct 2013 11:30, David Demelier demelier.da...@gmail.com wrote:
Hello there,
I'm writing because after a power failure I was unable to log in on my
FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some
files disappeared, including /etc/pwd.db. Thus I was unable to log in.
On 13.10.2013 12:16, CeDeROM wrote:
On 13 Oct 2013 11:30, David Demelier demelier.da...@gmail.com
mailto:demelier.da...@gmail.com wrote:
Hello there,
I'm writing because after a power failure I was unable to log in on my
FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some
On 13.10.2013 12:16, CeDeROM wrote:
On 13 Oct 2013 11:30, David Demelier demelier.da...@gmail.com
mailto:demelier.da...@gmail.com wrote:
Hello there,
I'm writing because after a power failure I was unable to log in on my
FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but
32 matches
Mail list logo
