On 2013-02-21, at 7:57 AM, Ric Wheeler wrote:
> On 02/21/2013 02:51 PM, Myklebust, Trond wrote:
>> On Thu, 2013-02-21 at 12:37 +0100, Ric Wheeler wrote:
>>> We have debated the need to have a system call to allow for offloading copy
>>> operations, for example to an NFS server (part to the new NFS
s already,
and while I'm not sure what kernel it is for the JBD code rarely changes
much
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
;j_committing_transaction->
> - t_outstanding_credits;
> + t_nr_buffers;
Same...
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
o complex, but
hiding the details of /dev/mem_notify from applications is desirable.
A simple wrapper (possibly part of glibc) to return the poll fd, or set
up the signal is enough.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscr
On 2013-10-02, at 9:38 AM, T Makphaibulchoke wrote:
> Instead of allowing only a single atomic update (both in memory and on disk
> orphan lists) of an ext4's orphan list via the s_orphan_lock mutex, this
> patch allows multiple updates of the orphan list, while still maintaing the
> integrity of
On 2013-10-02, at 9:36 AM, T Makphaibulchoke wrote:
> Adding new members, i_prev_oprhan to help decoupling the ondisk from the
> in memory orphan list and i_mutex_orphan_mutex to serialize orphan list
> updates on a single inode, to the ext4_inode_info structure.
What do these additional fields do
On 2013-10-02, at 9:36 AM, T Makphaibulchoke wrote:
> Instead of using a single per super block mutex, s_orphan_lock, to serialize
> all orphan list updates, a separate mutex and spinlock are used to
> protect the on disk and in memory orphan lists respecvitely.
>
> At the same time, a per inode
On 2013-09-04, at 10:39 AM, T Makphaibulchoke wrote:
> This patch intends to improve the scalability of an ext filesystem,
> particularly ext4.
In the past, I've raised the question of whether mbcache is even
useful on real-world systems. Essentially, this is providing a
"deduplication" service f
On 2013-09-05, at 3:49 AM, Thavatchai Makphaibulchoke wrote:
> On 09/05/2013 02:35 AM, Theodore Ts'o wrote:
>> How did you gather these results? The mbcache is only used if you
>> are using extended attributes, and only if the extended attributes don't fit
>> in the inode's extra space.
>>
>> I
On 2013-09-06, at 6:23 AM, Thavatchai Makphaibulchoke wrote:
> On 09/06/2013 05:10 AM, Andreas Dilger wrote:
>> On 2013-09-05, at 3:49 AM, Thavatchai Makphaibulchoke wrote:
>>> No, I did not do anything special, including changing an inode's size. I
>>> just used t
On 2012-12-04, at 13:24, Dave Chinner wrote:
> On Tue, Dec 04, 2012 at 01:56:39AM +0800, yangsheng wrote:
>> Relatime should update the inode atime if it is more than a day in the
>> future. The original problem seen was a tarball that had a bad atime,
>> but could also happen if someone fat-fing
fat-fingers a "touch". The future atime will never be fixed.
>>
>> Without relatime enabled, a future atime is updated to the current
>> kernel time on access. Relatime is meant to reduce the frequency
>> of atime updates, not decide if whether the system clock or the
>
On 2013-06-23, at 0:07, Namjae Jeon wrote:
> From: Namjae Jeon
>
> This patch series introduces 2 new ioctls for ext4.
>
> Truncate_block_range ioctl truncates blocks from source file.
How is this different from fallocate(FALLOC_FL_PUNCH_HOLE)? That is already in
existing kernels, and porta
On 2013-06-23, at 0:07, Namjae Jeon wrote:
> From: Namjae Jeon
> The EXT4_IOC_TRUNCATE_BLOCK_RANGE removes the data blocks lying
> between [start, "start + length") and updates the logical block numbers
> of data blocks starting from "start + length" block to last block of file.
> This will main
On 2013-08-04, at 5:48 PM, Dave Chinner wrote:
> On Sat, Aug 03, 2013 at 10:21:14PM -0400, Jörn Engel wrote:
>> On Sat, 3 August 2013 20:33:16 -0400, Theodore Ts'o wrote:
>>>
>>> P.P.S. At least in theory, nothing of what I've described here has to be
>>> ext4 specific. We could implement this
On 2013-07-18, at 1:07 PM, Al Viro wrote:
> On Thu, Jul 18, 2013 at 11:40:16AM -0700, Nathan Rutman wrote:
}
RETURN(rc);
}
What is going on here? We cast something to struct super_block *?
Where does it come from? The function it's in is
On 2013-05-14, at 0:25, Daniel Phillips
wrote:
> Interesting, Andreas. We don't do anything as heavyweight as
> allocating an inode in this path, just mark the inode dirty (which
> puts it on a list) and set a bit in the inode flags.
The new inode allocation is only needed for the truncate-to-ze
On 2013-03-30, at 12:49 PM, Pavel Machek wrote:
> Hmm, really? AFAICT it would be simple to provide an
> open_deleted_file("directory") syscall. You'd open_deleted_file(),
> copy source file into it, then fsync(), then link it into filesystem.
>
> That should have atomicity properties reflected.
On 2013-03-30, at 16:21, Ric Wheeler wrote:
> On 03/30/2013 05:57 PM, Myklebust, Trond wrote:
>> On Mar 30, 2013, at 5:45 PM, Pavel Machek
>> wrote:
>>
>>> On Sat 2013-03-30 13:08:39, Andreas Dilger wrote:
>>>> On 2013-03-30, at 12:49 PM, Pavel Machek
On 2013-03-10, at 6:06, Lijo Antony wrote:
> On 03/10/2013 08:51 AM, Simeon Bird wrote:
>>
>> We (nepomuk) recently looked at using fanotify, and indeed we would
>> need user watches, support for moves and recursive directory watches
>> (we need to support the case where /home is not a separate f
On 2012-08-22, at 12:00 AM, NeilBrown wrote:
> On Wed, 22 Aug 2012 11:57:02 +0800 Yuanhan Liu
> wrote:
>>
>> -#define NR_STRIPES 256
>> +#define NR_STRIPES 1024
>
> Changing one magic number into another magic number might help your case, but
> it not really a general solution.
turn on features in the JBD superblock.
Similarly, for 64-bit support in ext4 uses journal_set_features() to set
a 64-bit feature flag in the journal superblock.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send
Feb 2008 19:15:25 +0900.
[PATCH] ext3,4:fdatasync should skip metadata writeout when overwriting
It may be that we already have a solution in that patch for database
workloads where the pages are already allocated by avoiding the need
for ordered mode journal flushing in that case.
gt;fd:file descriptor of mountpoint
>FITHAW:Request cord for unfreeze
You may as well make the common ioctl the same as the XFS version,
both by number and parameters, so that applications which already
understand the XFS ioctl will work on other filesystems.
Cheers, Andreas
--
Andreas D
On Feb 26, 2008 08:39 -0800, Eric Sandeen wrote:
> Takashi Sato wrote:
>
> > o Elevate XFS ioctl numbers (XFS_IOC_FREEZE and XFS_IOC_THAW) to the VFS
> > As Andreas Dilger and Christoph Hellwig advised me, I have elevated
> > them to include/linux/fs.h as below.
cing reboot.
Actually, this is not true. Reiserfs will only prevent corruption of the
filesystem metadata. It does not guarantee that the file contents are
valid if they are being changed when the system crashes.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a
caches filling up the memory on a 1GB machine. However, there was
also a patch to fix for this posted to this list recently.
PPS - can you try and keep comments within 80 columns?
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would the
l stay in kernel memory until
it is flushed out with more messages (which itself might be detectable).
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?"
htt
ns would inherit this
trait. There are probably standard ways that processes inherit or drop
other priveleges (i.e. capabilities), so no point in inventing something
new. I just wanted to point out that not everything should inherit this.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a poun
add the index after we grow past 1 block")? Namely, don't
all directories get an index block (especially those growing larger than
1 block), or do you need to "chattr" each directory which will get an index?
If e2fsck gets into the picture with a COMPAT flag, I would think it will
bui
dynamic loading of backends (i.e. "device
drivers"), network device access, GUI/text front ends, etc). I believe it
is also being used for other high-end image acquisition devices, not just
scanners.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound
robably should be some way to suppress
> the automatic index addition, for example, when a user has a partition
> that's 100% full.
Yes, I was basically thinking that index creation would be done after the
rest of the filesystem had already been checked and was in a valid
dev[2]);
+ pdev[2] = pci_find_device(PCI_VENDOR_ID_ARTOP,devid[h],pdev[2]);
if (pdev[2] == NULL || pci_enable_device(pdev[2])) {
h++;
index = 0;
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of
+
+0xFE 00-9F Logical Volume Manager <mailto:[EMAIL PROTECTED]>
--
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/
SCSI_IOCTL_GET_IDLUN 0x5382/* conflicts with CDROMAUDIOBUFSIZ */
/* Used to turn on and off tagged queuing for scsi devices */
--
Andreas Dilger TurboLabs filesystem development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
patches floating around on l-k which addressed these issues.
Seems it is time to try them out, which I hadn't before because I wasn't
having any problems myself until now.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
sly better.
Yes, it appears that this would be a bug. We were only _checking_
"count" dentries, rather than pruning "count" dentries.
Testing continues.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ wo
to the situation you
describe (i.e. negative count). I first thought this was a bug, but then
realized for priority 0 (i.e. highest priority) we want to check the whole
dentry_unused list for unreferenced dentries.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a
irectories). In that case, how do we make
e2fsck create indexes for old filesystems when the DIR_INDEX compat flag
is turned on in the superblock?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving hi
the authority on
this). The kernel ext2_fs.h is out of date compared to the one in e2fsprogs.
The EXT3_FEATURE_COMPAT_HAS_JOURNAL and EXT2_FEATURE_COMPAT_IMAGIC_INODES
is missing from the kernel header.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipa
es, I have thought about this as well. If it is possible (I'm not sure
how, maybe a hashed per-super cache?) you could keep a pointer to the first
free entry in a directory, along with the dentry size and the mtime of the
directory. You could use this cache at dentry insertion time (validating
it by s
RAID problem.
Note, can you boot from one of the separate RAID drives with the Debian
LILO directly? Have you tried CHS, LBA32, and linear options to lilo?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would
group is a multiple of inodes_per_block
> or it isn't guaranteed?
mke2fs will always set up the filesystem this way, and there is no real
reason NOT to do that. If you are using a filesystem block for the inode
table, it is pointless to leave part of it empty, because you can't use
it
aining)
There is no reason to only have 1 or 2 or 17 inodes in this block. If we
assume we are not crossing a block boundary with the inode, then
inodes_per_group = n * inodes_per_block, where n = number of inode blocks.
Cheers, Andreas
PS - is this a code cleanup issue, or do you have some reaso
M support working
already, so no user tools needed for VG/LV activation. Granted, they don't
yet have tools to create/modify VG/LVs, but I think I can help them there.
It appears more likely that EVMS will only support Linux LVM volumes for
compatibility, and move to a more robust on-disk fo
asked you a couple of times on this, I would have already sent a
whole bunch of bug fixes to Linus as small, self-contained patches. However,
I held back because you asked me not to send patches to Linus directly.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a p
would really, really like to end up with accurate description of
> inode table layout somewhere in Documentation/filesystems. Heck, I
> volunteer to write it down and submit into the tree ;-)
I can write a few words as well.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of
n.edu.au/~jn/linux/Explore2fs.htm
-DOS client ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2/
RISC OS client ftp://ftp.barnet.ac.uk/pub/acorn/armlinux/iscafs/
+
+(*) no longer actively developed/supported (as of Apr 2001)
--
Andreas Dilger \ "If a man ate a pound of pas
_REV is also 1. Unless we run out of compat
flags or something, I don't see any reason why we would ever want to go
to rev 2.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hun
, or time out. Once
the database is up-to-date, it simplifies the job of keeping maintainers
(and other interested parties) in the loop.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still h
the code again in the future. I enable it sometimes when I'm doing
ext2 development, but it may not be worthy of a separate config option
that 99.9% of people will just be confused about.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
ely (and efficiently) use external
filesystem modules without the need to recompile the kernel. Granted,
if the external filesystem doesn't use more than the largest .u struct,
then it is currently possible as well, but that number changes, so it
is not safe.
Cheers, Andreas
--
Andreas Dilger
No point in punishing all users for filesystems they don't necessarily use.
Even for people that DO use NFS and/or HFS, they are probably still wasting
10k inodes * 108 bytes = 1MB of RAM for no good reason (because most of
their inodes are probably not NFS and/or HFS).
Cheers, Andreas
--
slab cache if it is a module?
Should uncommon-but-widely-used things like socket and shmem have their
own slab cache, or should they just allocate from the generic size-32 slab?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
of the fields
initialized, because the union field is zeroed for us, but slab is not.
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
ic clear_inode() from
a socket? In that case, the socket would just hold a pointer to the
fs-specific inode_info inside its own struct socket until the inode
is dropped.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\
rmation.
Try the following for a searchable mailing list:
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:
or
as a cop-out if any directory has a hash version not equal to the current
one we re-hash all the entries in the directory.
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?&quo
nd only fixing
the LVM devfs code (which is probably still broken in other ways). Heinz
decided to update the IOP instead. Note that with the new library build,
it is possible to have multiple IOP tools installed at the same time, and
the correct ones are chosen at runtime based on the kernel I
give 20-byte (or 88-byte) dirents for ext3, reducing the files count
to 4857 and 621792 (or 78183 and 40029696 for 4k filesystems) at 75% full.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him s
This is an e2fsck message, indicating you may have a corrupt superblock,
or the superblock has unsupported features. Which version of e2fsck do
you have?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, l
which
means each improvement is stable and reliable much quicker than if you
were to code a new filesystem from scratch for each new feature.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still
Daniel Phillips writes:
> Andreas Dilger wrote:
> > I was just doing the math for 1k ext2 filesystems, and the numbers aren't
> > nearly as nice. We get:
> >
> > (1024 / 16) * 127 * .75 = 6096 # 1 level
> > (1024 / 16) * 128 * 127
0, inode=0, rec_len=0,
> name_len=0
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 unsubsc
the next-level
index.
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 unsubscribe from this l
n 2.2? If so, then having these entries on disk will be important
for 2.2 compatibility, and you don't want to have different on-disk formats
between 2.2 and 2.4.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
ail/?group_id=20426
>
> Unfortunately maillist archives at sourceforge do not work.
Yes, I noticed this as well - there are several bug reports open already.
I have subscribed some of the mailing lists at sourceforge that I'm using
to marc.theaimsgroup.com, which has good searching facilit
xing will be used
in an "average" system.
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/ -- Do
, even if all of the files are gone.
All blocks used by the index also appear (in the proposed layout) as
regular directory blocks, so a non-index kernel can use them at any time
(of course the index is destroyed in this case).
As an aside, lost+found is NOT a "special" name in any way
r of existing
e2fsck anyways.
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
corrupt (the -n option means e2fsck will not fix the filesystem), and then
run "debugfs /dev/X", type "dump " and "ncheck inode_number"
at the prompt (note you NEED the <> around the inode number for dump).
Send the output.
Cheers, Andreas
--
And
c.)
There is a tool called gpart which will search a disk for filesystem
headers and such, and will optionally re-build your partition table
(if it is corrupted). You should give it a try.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
om the running kernel.
>
> Is it possible to do the same thing in Linux?
See IBM "dprobes" project. It is basically what you are describing
(AFAIK). It makes sense, because a lot of the OS/2 folks are now working
on Linux.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate
bh = sb->u.ext2_sb.s_inode_bitmap[bitmap_nr];
-
- is_directory = S_ISDIR(inode->i_mode);
-
- /* Do this BEFORE marking the inode not in use */
- clear_inode (inode);
/* Ok, now we can actually update the inode bitmaps.. */
if (!ext2_clear_bit (bit, b
covered, the tree can be rebuilt.
Actually, with Daniel's implementation, the index blocks will be in
the same file as the directory leaf nodes, so there should be no problem
in losing leaf blocks after a crash (not more so than the current ext2
setup).
Cheers, Andreas
--
Andreas Dilger \ &q
en delete these files. Sometimes there is a
problem with files > 2GB in size, but there should be no
problems with block special or pipes. What sort of errors do
you get, and is there anything in syslog?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of a
1 for them, is it OK with you?
>
> 0 is used for padding, so 1 makes sense, yes.
Sorry, but what are whiteouts? Inode 1 in ext2 is the bad blocks inode,
so it will never be used for a valid directory entry, but depending on
what it is we may want to make sure e2fsck is OK with it as well.
Ch
nto the filesystem (rather than "actions" to be done), it
doesn't matter how many times it is done. The recovery flags are not
reset until after the journal replay is completed.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
pcoming to allow LVM snapshots on ext3
filesystems, so there is little legitimate need for a dirty journal on
a read-only device.
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?&q
into the kernel each time, which does copy_from_user(),
so the fact that strtok() breaks the data is OK. The only time this
is bad is with Stephen's ext3 rootflags option...
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\
em
again to run the program.
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 unsubscribe
res << bits;
+ if (res > (512LL << 32) - (1 << bits))
+ res = (512LL << 32) - (1 << bits);
+ return res;
+}
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they c
Al Viro writes:
> Andreas Dilger wrote:
> > Actually, this is wrong. The ext2 inode limit is 2^32 512-byte sectors,
> > not 2^32 blocksize blocks. Yes this is a wart and Ted wants to fix it, as
>
> ??? Where? Oh, wait... ->i_blocks? I'ld rather refuse to grow p
s in an unused kernel tree.
The sequence of events leading to this bug would help a great deal...
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.
it is best to
have only 1 partition for the whole disk. It wastes less space.
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/adilg
Paul Jakma writes:
> On Wed, 10 Jan 2001, Andreas Dilger wrote:
> > You should also get the LVM user tools from CVS (with TAG LVM_0-9-patches)
> > to solve this problem. There will hopefully be a new LVM release soon.
>
> any word on when the kernel fixes are going to lin
t be unmounted, and hence root is also
busy and can't be ro remounted. Maybe also check /proc/mounts for "none".
> umount: /: device is busy
> Remounting root-filesystem read-only
> mount: / is busy
> Rebooting.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a poun
f sync...
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 unsubscribe from this list: send
t a search
of l-k should locate it. Depending on when last you fsck'd your filesystem,
you may have already had some of these disk problems. However, there was
another report recently on 2.4.0 that looked the same, and that user had
just e2fsck'd his filesystem before booting 2.4.0 for the
in dozens of utilities (e.g. LILO,
mount, fsck, dump, etc).
One reason why this may NOT ever make it into the kernel is that I know
"kernel poking at devices" is really frowned upon.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
gt; ID1=sdb
> ID2=sdc
There are not enough major/minor numbers to do this.
> Then, it is possible that we must change /etc/fstab
If you are using ext2 (or ext3), it is possible to mount by filesystem
LABEL or UUID. See man pages for e2label/tune2fs/dumpe2fs/mount(8)/fstab(5).
Cheers, Andrea
rblock feature. Even so, it is only a matter of turning the
sparse_super flag on or off and running e2fsck on the filesystem to convert.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, l
really. You have to poke each drive to get the serial
number. What if they are IDE or SCSI or FCAL or RAID array? Probably
reading a block from a disk is safer than trying to find the drive
serial number.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of
#x27;ve re-worked it and will post after testing a bit.
My only hesitation was that kernel probing is frowned upon. When UUID/LABEL
support for devfs came up at the Miami Linux Storage Workshop, it was
given the thumbs down.
If I get a chance I will also fix LILO to allow UUID/LABEL for root as well.
BIOS drive, and
would match search for a UUID or LABEL as the root device. If /etc/fstab
is also handled exclusively with UUID or LABEL (or LVM), then you don't
care what the drives are called (excluding swap, hmmm, maybe we can add
a signature to swap?).
Cheers, Andreas
--
Andreas Dilger \ &q
David Balazic writes:
> Andreas Dilger <[EMAIL PROTECTED]> wrote :
> > In the end I re-wrote most of the patch, so
> > that we resolve ROOT_DEV before calling mount_root(), just to be a bit
> > more consistent. I will release a new patch for 2.2.18 and 2.4.0 after
>
know which array should be /dev/md0? What if you had a
second array on /dev/hdb and /dev/hdd, would that become /dev/md0 (assuming
it had a kernel/boot sector)?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\
it breaks every filesystem that isn't part of
the kernel. That said, the addition of (reiserfs-specific) read_inode2
and dirty_inode pointers also break all non-kernel filesystems. Argh!
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
omething along these lines as well
(i.e. direct device-device communication).
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/
ve renaming by 99%. It goes from "each time drives
are added/moved/removed my system may be broken" to "if I insert two
drives with the same label 50% chance my system is broken". I'll take
the latter any day.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a poun
1 - 100 of 654 matches
Mail list logo
