- 06 Jan, 2006 40 commits
-
-
Evgeniy authored
This patch should fix compilation failure of fs/ufs/dir.c with defined UFS_DIR_DEBUG Signed-off-by:
Evgeniy Dushistov <dushistov@mail.ru> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Dimitri Sivanich authored
This greatly reduces the amount of memory used by mmtimer on smaller machines with large values of MAX_COMPACT_NODES. Signed-off-by:
Dimitri Sivanich <sivanich@sgi.com> Signed-off-by:
Christoph Lameter <clameter@sgi.com> Signed-off-by:
-
Adrian Bunk authored
Randy Dunlap: "Dave is no longer at OSDL and is no longer maintaining that driver." Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
git://brick.kernel.dk/data/git/linux-2.6-blockLinus Torvalds authored
Manual fixup for merge with Jens' "Suspend support for libata", commit ID 9b847548. Signed-off-by:
-
Linus Torvalds authored
This was harmless, but for the case of a device that had no irq pre-defined we would incorrectly suggest that "usepirqmask" might make a difference. It never would, and the message was just confusing people. Reported in the dmesg of Etienne Lorrain. Signed-off-by: -
Jens Axboe authored
This patch adds suspend patch to libata, and ata_piix in particular. For most low level drivers, they should just need to add the 4 hooks to work. As I can only test ata_piix, I didn't enable it for more though. Suspend support is the single most important feature on a notebook, and most new notebooks have sata drives. It's quite embarrassing that we _still_ do not support this. Right now, it's perfectly possible to suspend the drive in mid-transfer. Signed-off-by:
Jens Axboe <axboe@suse.de> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
NeilBrown authored
Also export current (average) speed and status in sysfs. Signed-off-by:
Neil Brown <neilb@suse.de> Acked-by:
Greg KH <greg@kroah.com> Signed-off-by:
-
NeilBrown authored
Writing major:minor to md/new_dev will bind that device to the array. Signed-off-by:
-
NeilBrown authored
Signed-off-by:
-
Andrew Morton authored
drivers/md/md.c: In function `offset_show': drivers/md/md.c:1670: warning: long long unsigned int format, different type arg (arg 3) Cc: Neil Brown <neilb@suse.de> Signed-off-by:
-
NeilBrown authored
Signed-off-by:
-
NeilBrown authored
This the role that a device has in an array can be viewed and set. Signed-off-by:
-
NeilBrown authored
Move the checks - that dev size is never less than array size - into bind_rdev_to_array to make sure it always happens properly (there is one place where currently it doesn't). Also reject any superblock which claims an array size smaller than the device in question can hold. Signed-off-by:
-
NeilBrown authored
If array is active, try to reshape, else just set the value. Signed-off-by:
-
NeilBrown authored
Store this total in superblock (As appropriate), and make it available to userspace via sysfs. Signed-off-by:
-
NeilBrown authored
Signed-off-by:
-
NeilBrown authored
Allow it to be set to a particular version, or 'none'. Signed-off-by:
-
NeilBrown authored
Signed-off-by:
-
NeilBrown authored
... only before array is started of course. Signed-off-by:
-
NeilBrown authored
When we do a user-requested check/repair, we lose count of the outstanding requests... Also make sure that when anything is written to md/sync_action, the RECOVERY_NEEDED flag is set and the thread is woken up so any changes take effect. Signed-off-by:
-
NeilBrown authored
When we update a page_cache page in the kernel, we need to flush_dache_page or userspace might not see the change. Signed-off-by:
-
Adrian Bunk authored
Make the needlessly global function md_new_event() static. Signed-off-by:
-
NeilBrown authored
.. because they aren't used outside md.c Signed-off-by:
-
NeilBrown authored
Signed-off-by:
-
NeilBrown authored
Commands written to sysfs files may, or my not, be \n terminated. We want to accept with case. For this we use cmd_match. Signed-off-by:
-
NeilBrown authored
md sometimes call put_page on NULL pointers (treating it like kfree). This is not safe, so define and use a 'safe_put_page' which checks for NULL. Signed-off-by:
-
NeilBrown authored
The kernel should not be imposing these policy limits: The time between bitmap updates should certainly be allowed to be more than 15 seconds, and if someone wants a bitmap chunk size in excess of 4MB, the kernel isn't the place to stop them. Signed-off-by:
-
NeilBrown authored
The code to overwrite/reread for addressing read errors in raid1/raid10 currently assumes that the read will not alter the buffer which could be used to write to the next device. This is not a safe assumption to make. So we split the loops into a overwrite loop and a separate re-read loop, so that the writing is complete before reading is attempted. Cc: Paul Clements <paul.clements@steeleye.com> Signed-off-by:
-
NeilBrown authored
md supports multiple different RAID level, each being implemented by a 'personality' (which is often in a separate module). These personalities have fairly artificial 'numbers'. The numbers are use to: 1- provide an index into an array where the various personalities are recorded 2- identify the module (via an alias) which implements are particular personality. Neither of these uses really justify the existence of personality numbers. The array can be replaced by a linked list which is searched (array lookup only happens very rarely). Module identification can be done using an alias based on level rather than 'personality' number. The current 'raid5' modules support two level (4 and 5) but only one personality. This slight awkwardness (which was handled in the mapping from level to personality) can be better handled by allowing raid5 to register 2 personalities. With this change in place, the core md module does not need to have an exhaustive list of all possible personalities, so other personalities can be added independently. This patch also moves the check for chunksize being non-zero into the ->run routines for the personalities that need it, rather than having it in core-md. This has a side effect of allowing 'faulty' and 'linear' not to have a chunk-size set. Signed-off-by: -
NeilBrown authored
Signed-off-by:
-
NeilBrown authored
...because that seems to be the preferred practice these days. Signed-off-by:
-
NeilBrown authored
Signed-off-by:
-
NeilBrown authored
- replace open-coded hash chain with hlist macros - Fix hash-table size at one page - it is already quite generous, so there will never be a need to use multiple pages, so no need for __get_free_pages No functional change. Signed-off-by:
-
NeilBrown authored
Replace multiple kmalloc/memset pairs with kzalloc calls. Signed-off-by:
-
NeilBrown authored
Substitute: page_cache_get -> get_page page_cache_release -> put_page PAGE_CACHE_SHIFT -> PAGE_SHIFT PAGE_CACHE_SIZE -> PAGE_SIZE PAGE_CACHE_MASK -> PAGE_MASK __free_page -> put_page because we aren't using the page cache, we are just using pages. Signed-off-by:
-
NeilBrown authored
With this patch it is possible to poll /proc/mdstat to detect arrays appearing or disappearing, to detect failures, recovery starting, recovery completing, and devices being added and removed. It is similar to the poll-ability of /proc/mounts, though different in that: We always report that the file is readable (because face it, it is, even if only for EOF). We report POLLPRI when there is a change so that select() can detect it as an exceptional event. Not only are these exceptional events, but that is the mechanism that the current 'mdadm' uses to watch for events (It also polls after a timeout). (We also report POLLERR like /proc/mounts). Finally, we only reset the per-file event counter when the start of the file is read, rather than when poll() returns an event. This is more robust as it means that an fd will continue to report activity to poll/select until the program clearly responds to that activity. md_new_event takes an 'mddev' which isn't currently used, but it will be soon. Signed-off-by:
-
NeilBrown authored
Add in correct read-error handling for resync and read-only situations. When read-only, we don't over-write, so we need to mark the failed drive in the r10_bio so we don't re-try it. During resync, we always read all blocks, so if there is a read error, we simply over-write it with the good block that we found (assuming we found one). Note that the recovery case still isn't handled in an interesting way. There is nothing useful to do for the 2-copies case. If there are 3 or more copies, then we could try reading from one of the non-missing copies, but this is a bit complicated and very rarely would be used, so I'm leaving it for now. Signed-off-by:
-
NeilBrown authored
Largely just a cross-port from raid1. Signed-off-by:
-
NeilBrown authored
We are inadvertently setting the R1BIO_Uptodate bit on read errors when we decide not to try correcting (because there are no other working devices). This means that the read error is reported to the client as success. Signed-off-by:
-
NeilBrown authored
Where performing a user-requested 'check' or 'repair', we read all readable devices, and compare the contents. We only write to blocks which had read errors, or blocks with content that differs from the first good device found. Signed-off-by:
-
