/etc/rc.local
>
> mount -t vfat /dev/hdb1 /hard2
> mount -t vfat /dev/hdb5 /hard4
> mount -t vfat /dev/hdc1 /hard3
> mount -t vfat /dev/hda1 /hard1
Out of curiosity, why not just put them into /etc/fstab?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound o
configurable makes it even harder for a cracker to know
what affects the entropy pool.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/a
(ROOT_DEV));
mount_it:
printk ("VFS: Mounted root (%s filesystem)%s.\n",
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/
"[NEW DRIVER] New user space serial port"
which does just what you want. Just-in-time kernel development has arrived.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungr
Al Viro writes:
> (x>>33) is the same as (x / (1LL<<33)). I.e. _with_ your change it
> becomes "file >= 8Gb", instead of the current (correct) "file >= 2Gb".
OOPS. My bad. You are right. Time to hide head in sand.
Cheers, Andreas
--
Andreas
t) >> 33) &&
!EXT3_HAS_RO_COMPAT_FEATURE(sb,
EXT3_FEATURE_RO_COMPAT_LARGE_FILE)) {
/* If this is the first large file created, add a flag
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto
bits - 2)) + \
+ (1LL << (bits - 2)) * (1LL << (bits - 2)) + \
+ (1LL << (bits - 2)) * (1LL << (bits - 2)) * (1LL << (bits - 2))) * \
+(1LL << bits)) - 1, 512LL * ((1LL << 3
"bit already set for inode %d", j);
goto repeat;
}
*/
# Need to check that we got a good gdp back here...
> +fail2:
> + gdp = ext2_get_group_desc (sb, i, &bh2);
if (!gdp)
goto fail;
> + gdp
Andrea writes:
> On Thu, Nov 30, 2000 at 01:05:53PM -0700, Andreas Dilger wrote:
> > the RAID and LVM make_request functions should be changed to do that
> > instead (i.e. 0 on success, -ve on error, and maybe "1" if they do their
> > own recursion to break the loop
vance!
UDF is an extra patch for 2.2 kernels (it _may_ be in 2.2.18, I don't recall).
It is standard on 2.4. You can get the UDF patches at sourceforge, IIRC.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they ca
ed to other kernel
functions. Normally, we return 0 on success, and -ve on error. Maybe
the RAID and LVM make_request functions should be changed to do that
instead (i.e. 0 on success, -ve on error, and maybe "1" if they do their
own recursion to break the loop)?
if your "dd" is actually seeking, or
just pretending to... Maybe an strace of the "dd" call will tell us if
it is screwing with our minds. Also, if you could make a scratch ext2
filesystem with 1k blocks, and see if it does the same thing. Even
better would be to try a different ker
driver for all
of the kernel versions, so they don't have to bugfix each driver version.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucal
7;t really worry about it.
I think the scenario where you have a large amount of space in directories
that will never be used again is very unusual and should not be a reason
to make the code more complex.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of ant
47515 47516 47517 47518 47519 47520 ... 48723 48724
TOTAL: 983
^^^ these are ext2fs sized blocks, not necessarily kB
If what debugfs says doesn't match du, then it is du/libc/stat that is
broken. If debugfs says the file actually has 600 bytes of data,
then it is the filesystem tha
e
http://marc.theaimsgroup.com/?l=linux-kernel&r=1&w=4
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbe
tem where root != god.
> root should be able to do fork() regardless of any limits,
> and IMHO the following patch is the right thing.
Then set the rlim_cur to unlimited, and blow your system up as you like.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a poun
ly already
done so). If you haven't done a full fsck on this filesystem in a long
time, there is a chance the corruption was from the old kernel bug.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ w
.
The current (0.0.5b) ext3 code is doing pretty good, and if you use
metadata-only journalling it is about as fast as ext2. I still wouldn't
use this on a production system where data loss is fatal, although I
have never had any data loss or filesystem corruption because of ext3.
Cheers, Andr
en for ext3, and no complaints at least
from Ted (he is aware of the issues).
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/Peopl
block filesystem, this would
happen at 524 TB. With sparse filesystems, the metadata will only
take a small percentage of the available space.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, lea
e middle of "if" blocks, etc?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubs
t think the IDE code is ready for hot-swap yet.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
sb->u.ext2_sb.s_es->s_state = cpu_to_le16(sb->u.ext2_sb.s_mount_state);
> mark_buffer_dirty(sb->u.ext2_sb.s_sbh);
> }
> db_count = sb->u.ext2_sb.s_db_per_group;
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
question (actually the
InterMezzo distributed filesystem uses the ext3-jfs functionality to
do compound transactions on disk to ensure cluster coherency).
I think that Stephen at one time said he would change the name, but I
guess he has not done so yet.
Cheers, Andreas
--
Andreas Dilger \ "
nd obdfs/super.c (init_module, init_obdfs, cleanup_module) at:
ftp://ftp.stelias.com/pub/obd/obd-0.004.tgz
This module also does slab-cache initialization and cleanup (properly!),
so that is also worth looking at.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and
machine
- can also print logs to printer
http://www-miaif.lip6.fr/willy/pub/linux-patches/kmsgdump/
It has a 2.2 and 2.3 version (nothing recently, probably because of 2.4
freeze). It would probably be a prime candidate for the "loadable SysRq
modules" patch that has been posted
ct that such a patch wouldn't make it into 2.2 or 2.4. I also
don't see why you want to have a strangely formatted floppy, since even
a regular 1.44 format will hold your proposed maximum 1MB buffer. Since
the printk buffer is pinned kernel memory, you probably don't want that
an
rs that have multiple
major numbers registered (per Documentation/devices.txt). Some of
the storage drivers have been allocating blocks of 8 major numbers at
a time.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they ca
your own) to really support LFS.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscrib
__u32 lv_chunk_size;
__u32 lv_snapshot_minor;
+#ifdef __KERNEL__
struct kiobuf * lv_iobuf;
struct semaphore lv_snapshot_sem;
struct list_head * lv_snapshot_hash_table;
-unsigned long lv_snapshot_hash_mask;
+ulong lv_snapshot_hash_mask;
+#else
+char dummy[200];
+#e
r 98304, 163840, 229376, 81920) to see
if that works. I think I will submit a patch to Ted which offers more
suggestions than 8193 for backup blocks, since not too many people know
where the backups are located on more recent filesystems since they
will normally have 4kB blocks these days.
Cheers,
nux-kernel and/or
linux-mm lists to see if they can find more about it. It may already
have been fixed.
One other thing to check is if this was the first oops, or if there was
an earlier one. It is usually the first oops that is the real problem,
and later ones do not really help much.
Cheers,
Sudhindra Herle, you write:
> I just got two separate crashes using 2.2.17 and reiserfs.
You should probably contact the reiserfs mailing list because reiserfs
is not in the official kernel.
> I have lost faith in reiserfs. So, I'll rebuild the kernel and move back
> to EXT2.
Oh well...
Cheers
to kill.
Having a SIGDANGER handler is good for 2 reasons:
1) Lets processes know when memory is short so they can free needless cache.
2) Mark process with a SIGDANGER handler as "more important" than those
without. Most people won't care about this, but init, and X, and
ative?
The GNU parted program is a partition-magic work-alike. I think you can
find it at parted.gnu.org.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mdds
oblem is with RAID doing buffer cache
snooping and causing data to be written out-of-order to disk (on 2.2).
This is fixed in 2.4, but there _may_ still be a problem in 2.4 when
rebuilding the array (on disk failure) in 2.4... I'm not too sure of
the latter though...
Cheers, Andreas
--
Andreas
chronization for reads (shared) and writes
> (exclusively) in the kernel. I assume it can be done it's just that I'm not
> sure how to do it yet. This is probably a very easy question.
There are read/write locks available in the kernel. Look in
include/linux/spinlock.h and include/linux/brlo
't think there is a problem, but watch out
for software RAID 5 and journalling filesystems (reiser or ext3, at least
under 2.2) - it can have problems if there is a disk crash.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
but as with regular
loopback devices, there is a 2GB limit.
I posted it to fsdevel a few months ago, but I have also uploaded it to:
ftp://ftp.stelias.com/pub/adilger/loopdiscard-2.2.16.patch
ftp://ftp.stelias.com/pub/adilger/loop_discard.c
The loop_discard.c program simply calls the ioctl to enable or disabl
lly like to
> use both simultaneously and to some testing.
There are some name conflicts between the ext3 and reiserfs patches,
namely journal_release() and buffer_journaled(). In my kernel code, the
reiserfs functions were renamed reiser_*(). Other than that they
should work together.
Ch
ad-only mounted fs, you don't have problems
with other programs changing the fs at the same time, but it is still
dangerous to change the superblock directly like this. Once you can
mount read-only, can you not also simply unmount the fs? What is it
you are trying to do?
Cheers, Andreas
--
ld be very grateful if someone could point out to me where the
> problem is - and tell me how to solve it :-)
When you have a dentry reference, you need to free it via dput(), so that
the kernel knows the file is no longer in use. This is the same with
iget() and iput() - you always need to fre
" at fsck time if the second dir block
is not written to disk, because no directory is referencing these inodes.
This would also explain why the direntry offset is pointing past the
end of the first dir block, because the next block was added at the time
the new file was created, but then later
ry->d_name.len > UFS_MAXNAMLEN)
return ERR_PTR(-ENAMETOOLONG)
should probably be changed back to:
if (dentry->d_name.len > EXT2_NAME_LEN)
return ERR_PTR(-ENAMETOOLONG)
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of
Mark Givens writes:
> Are there any tools/patches that allow for RAID disk and/or raw device
> accounting?
You can use Stephen Tweedie's "sard" patches, available at:
ftp://ftp.linux.org.uk/pub/linux/sct/fs/profiling/sard-0.6.tar.gz
--
Andreas Dilger \ "If a man
ecause
nobody ever tries such things due to reason of sanity... It may be
you are trying to do something which can better be done another way.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him s
Daniel writes:
> Alexander Viro wrote:
> > On Mon, 18 Sep 2000, Andreas Dilger wrote:
> > > This may actually be a problem in the future... what about shared access
> > > block devices like FCAL or a distributed filesystem? It has to be
> > > possible for pa
> problem.
Looking at this printk makes me think that this is better off in the man
page than in the kernel... Maybe you should just submit a patch which
removes the whole hpfs_help() function, and updates the mount(8) man page...
Cheers, Andreas
--
Andreas Dilger \ "If a man ate
goto tq_scheduler_back;
Does this have an impact on the system when not using reiserfs? What
is it that reiserfs does that affects the scheduler?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leavi
pport, but can be used for a variety of
other extensions to ext2. As Ted indicates, the EAs are stored in another
block, so it will reduce performance if the block is not already in
memory.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
email was delivered to the reiserfs mailing
list and then resent out to the kernel mailing list. Either it is an
issue at the reiserfs mailing list, or a problem at "[EMAIL PROTECTED]"
which is a real domain, despite the name.
Cheers, Andreas
PS - this note has been CC'd
Brian Hayward writes:
> I also think it's a logical conclusion that a patch to a GPL'd program is
> released under the GPL - even if you don't specifically say so.
Actually, this totally makes sense, because a patch contains "context" lines
and therefore includes GPL code in it - hence it MUST be
Theodore Ts'o writes:
> Dr. Michael Weller writes:
> > Sorry, I've no idea about the ext2 and fs implementation.
> > However did you read the comment below and convince yourself that 'err' is
> > always set correctly?
>
> I looked at it and was convinced.
Ted and I submitted patches to this e
601 - 654 of 654 matches
Mail list logo
