On Fri, 2009-03-27 at 22:55 +, Daniel Colascione wrote:
> The risk isn't data loss; if you forgo fsync, you accept the risk of
> some data loss. The issue that started this whole debate is consistency.
>
> The risk here is of the system ending up in an invalid state with zero-
> length files *
@nicobrainless: Sounds like a hardware failure to me. I'd suggest
investigating the smartctl utility (in the package 'smartmontools') to
check on the general health of the drive.
Note that this isn't a troubleshooting forum, nor is 'too many
comments' really a good excuse for not reading them.
Theo, does that then imply that setting the writeback time to the
journal commit time (5 seconds) would also largely eliminate the
unpopular behavior?
How much of the benefit of delayed allocation do we lose by waiting a
couple seconds rather than minutes or tens of seconds? Any large
write could
I just want to add another voice saying that I have been running ext4
in Jaunty with no problems. It has been excellent so far! Having a
backup is wise, but that is nothing new.
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
You received this bug notification because you are a member of
Well what I was asking was if whatever patch that negates the issues
described in this bug report is going to be a part of 9.04 or not. We
can't expect applications to change their behavior overnight, it can
take years. Certainly not even by Jaunty +3.
Would forcing all dot files to be written
@Jeremy:
If you look at the kernel docs, ext4 is considered stable. I personally
haven't seen a problem with several systems running ext4. It only becomes
an issue if your system is unstable and you're using software that "assumes"
ext3 (and older) behavior.
@all:
I believe that having ext4 "m
Tim, does that mean that the patches required to make EXT4 stable won't
be in the final release of Jaunty?
Tim Gardner wrote:
> Steve - I've no plan to add these patches as they are not part of the
> stable updates.
>
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
You received this bu
If 9.04 ships with this bug, EXT4 should be altogether removed or at
least not advertised in the feature list. Shipping a broken EXT4 with
9.04 would be a VERY bad move, and the press would have a field day.
Steve Langasek wrote:
> Tim, are there any plans to backport the fixes Ted mentions in c
I think the best solution is to move EXT3's behavior in this regard to
EXT4, then ask developers to use the new style to ween them off of the
old style little by little. Asking all applications to change isn't
going to happen, and using the EXT3 save style is the only forseeable
way right now.
Theodore Ts'o wrote:
> @Raine,
>
> Well, if the applications were written correctly, there wouldn't be any
> data loss problems. I suppose we could thank the unreliable proprietary
> binary drivers that were causing all of these crashes, so we could find
> out about the buggy application code.
On Tue, Mar 10, 2009 at 10:21 PM, Theodore Ts'o wrote:
> The fact that so many people are complaining is what
> makes me deeply suspicious that there may be some faulty applications
> out there which are constantly rewriting existing applications reguarly
> enough that people are seeing this --- e
@Theodore
iotop (in the repos already) may or may not be useful for this.
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Theodore, do you think we should try to be proactive about this and
encourage people to file bugs against applications which do this, and
tagging them with a specific tag for this?
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
You received this bug notification because you are a member
On Sat, Mar 7, 2009 at 12:03 PM, Theodore Ts'o wrote:
> I really wish Ubuntu had a "kernel of the week" or which provided the
> latest development kernel pre-packaged up, much like Fedora has. It
> would make it a lot easier to recommend that people try a newer kernel
> package.
@Ted-
We do!
h
The two files I have that are 0b are jpg images.
Michael Rooney wrote:
> Jeremy, as pablomme said: "there are very many files that have zero length
> under normal conditions, so it'll be very hard to tell if any file has been
> affected this way."
>
> Many people are reporting trashed gnome sessi
Jeremy, as pablomme said: "there are very many files that have zero length
under normal conditions, so it'll be very hard to tell if any file has been
affected this way."
Many people are reporting trashed gnome sessions so it should be fairly
obvious whether it is or not. A 0b file is definitely n
There are a couple files that are 0b, so this bug is affecting me. Is
there any information I can provide to help the developers?
Wade Menard wrote:
> find / -size 0b should be enough. Please keep further discussion not
> related to fixing this bug on a forum or mailing list.
>
--
Ext4 data los
Thank you. Please understand that my question was related to this bug,
as such a command will help me determine if this bug is affecting me,
then I could give more info that would help the fix.
Wade Menard wrote:
> find / -size 0b should be enough. Please keep further discussion not
> related to
I've not experienced the bug yet, though I've not had a chance to try
the script yet.
I was wondering if anyone knows of a terminal command I could run that
would give me a list of all the files on my system that are 0 KB. As far
as I know, I've never experienced this, but then again it may hav
I never had any trouble, but I installed Jaunty last week, after the fix
was released. Is it possible this bug now only affects those that
installed it prior to the fix? When did you guys install it?
I've moved over 100GB of files since I installed it. I had at least two
hard crashes, everythin
pablomme schrieb:
> @Christian: I understand that your system hung _before_ you rebooted
> into the updated kernel? If so, the changes wouldn't have taken effect,
> and the data loss was caused by the original kernel.
Well, there has not been any kernel update so far here. I am on:
2.6.28-7.20 fo
21 matches
Mail list logo
