On Jan 30, 2008 14:49 -0800, Andrew Morton wrote:
> > Problem Description:
> > On several occasions now I have had e2fsck prune away ACLs on my file
> > systems
> > during a file system check after rebooting a number of (reasonably) long
> > running Samba servers. This morning I decided to manual
Theodore Tso wrote:
You can manually set the flag using debugfs:
# debugfs -w /dev/hdXX
debugfs: set_super_value s_flags 4
debugfs: quit
(Or, if you're lazy, you can also type the shorthand "ssv flags 4" to
debugfs.)
With e2fsprogs 1.40.5, if the test_fs flag is set, then blkid w
The patch titled
ext3: fix lock inversion in direct IO
has been added to the -mm tree. Its filename is
ext3-fix-lock-inversion-in-direct-io.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c)
On Jan 30, 2008 11:19 -0600, Eric Sandeen wrote:
> This seems to work fine; any comments, either about
> the logic, or the text descriptions, or the various
> options I've shown/not shown?
>
> To test, copy your "magic" file somewhere local,
> replace the ext2/3 section with the following,
> and
On Wed, 30 Jan 2008 15:17:57 -0800
Mingming Cao <[EMAIL PROTECTED]> wrote:
> The buufer head pointer passed to journal_wait_on_commit_record()
> could be NULL if the previous journal_submit_commit_record() failed
> or journal has already aborted.
>
> We need to check the error returns from journa
The anaconda folks are now using blkid instead of hand-rolled
tests for filesystem type at install time, but they had one
more request:
Bugzilla Bug 409321: RFE: information on blkdevs "formatted" as PVs
https://bugzilla.redhat.com/show_bug.cgi?id=409321
The attached patch does the right thing fo
On Wed, 2008-01-30 at 12:00 -0800, Andrew Morton wrote:
>
> Begin forwarded message:
>
> Date: Wed, 30 Jan 2008 03:24:08 -0800 (PST)
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [Bugme-new] [Bug 9849] New: NULL pointer deref in
> journal_wait_on_commit_record
>
>
> http://bugzi
On Wed, 30 Jan 2008 14:29:27 -0800 (PST)
[EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9855
>
>Summary: ext3 ACL corruption
>Product: File System
>Version: 2.5
> KernelVersion: 2.6.23
> Platform: All
> OS/Version:
On Wed, Jan 30, 2008 at 11:26:20PM +0100, supersud501 wrote:
>
> how can i set this "flag" on my filesystem? i've never set any flags before
> so i just removed the code from ext4-module to mount my filesystems, but
> setting the flag once would make it easier i think :)
If you have e2fsprogs 1.
Theodore Tso wrote:
As discussed on RFC, this flag is simply a generic "this is a
crash/burn test filesystem" marker. If it is set, then filesystem
code which is "in development" will be allowed to mount the
filesystem. Filesystem code which is not considered ready for
prime-time will check for
Andreas Dilger wrote:
There is an e2fsprogs RPM that can check ext4 filesystems with extents,
available at ftp://ftp.lustre.org/pub/lustre/other/e2fsprogs/ (no
warranties, etc).
thanks for your answer. maybe i'll go testing this (haven't had anything
to do with rpm's yet, i'm on ubuntu).
Begin forwarded message:
Date: Wed, 30 Jan 2008 03:24:08 -0800 (PST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 9849] New: NULL pointer deref in
journal_wait_on_commit_record
http://bugzilla.kernel.org/show_bug.cgi?id=9849
Summary: NULL pointer deref i
On Jan 30, 2008 11:54 +0100, supersud501 wrote:
> i'm testing the ext4-filesystem for months now (no data loss experienced ),
> but i noticed e2fsck not being able to check a ext4-filesystem with extents
> ("e2fsck: Filesystem has unsupported feature(s)").
>
> i just pulled linus' kernel tree (w
supersud501 wrote:
> hello,
>
> i'm testing the ext4-filesystem for months now (no data loss experienced
> ), but i noticed e2fsck not being able to check a ext4-filesystem with
> extents ("e2fsck: Filesystem has unsupported feature(s)").
>
> i just pulled linus' kernel tree (with the newly add
This seems to work fine; any comments, either about
the logic, or the text descriptions, or the various
options I've shown/not shown?
To test, copy your "magic" file somewhere local,
replace the ext2/3 section with the following,
and do something like:
# file -C -m magic; file -m ./magic -s /dev
hello,
i'm testing the ext4-filesystem for months now (no data loss experienced
), but i noticed e2fsck not being able to check a ext4-filesystem with
extents ("e2fsck: Filesystem has unsupported feature(s)").
i just pulled linus' kernel tree (with the newly added patches to ext4)
and e2fspr
Hi,
resending the patch just in case you've missed it.
Honza
--
Jan Kara <[EMAIL PROTECTED]>
SUSE Labs, CR
---
Commit block was intended to have several copies of the header. But
due to a bug it never had them and actua
On Wed, 30 Jan 2008, Theodore Tso wrote:
>
> That's because you are doing a diff stat of changes that haven't been
> checked in yet. I was doing a "git log -p origin.. | diffstat -p1",
> and in that incantation you definitely do need the -p1 to diffstat.
You should *always* use "-p1" to diffst
Theodore Tso <[EMAIL PROTECTED]> writes:
> On Tue, Jan 29, 2008 at 10:54:03PM +0100, Jan Engelhardt wrote:
>>
>> I am seeing normal behavior:
>>
>> 22:52 sovereign:~/linux > git diff HEAD | diffstat
>
> That's because you are doing a diff stat of changes that haven't been
> checked in yet. I was
19 matches
Mail list logo
