Hi Franziska,
(2014/06/24 16:50), Franziska Näpelt wrote:
Hi,
i want to expand a btrfs filesystem. In the moment I have four 2 TB HDDs
for one btrfs pool.
I want to replace two of the HDDs with 3 TB devices. For this reason i
added as first one 3 TB device. After that, i do the btrfs delete
Hello Satoru,
here are your requested informations:
environment:
- four 2 TB disks: /dev/sd[c-f]
- two 3 TB disks: /dev/sdg (but until now, only one is connected)
filesystem consists of/dev/sd[c-f]
I wanted to replace /dev/sdc by /dev/sdg ( with commands add and after
that delete.
In the
Franziska Näpelt posted on Thu, 26 Jun 2014 13:06:35 +0200 as excerpted:
There are a lot of following messages:
btrfs free space inode generation (0) did not match free space cache
generation
Well, set of messages at least is somewhat expected after a hard
shutdown, and shouldn't be a
Hi Satoru,
I'm sorry, but the boot process is always runnig(i hope so), i can't
login until now. So therefore i have currently no logs.
I don't want to interrupt these process, because there are a lot of
fileactions on the harddrive (LED is blinking).
I'm not sure about the mkfs.btrfs option,
Franziska Näpelt posted on Thu, 26 Jun 2014 13:47:12 +0200 as excerpted:
What do you mean with if it seems the space_cache rebuild is
interfering with further activity for too long
The boot-process runs for five hours now. How long should i wait? What
would you recommend?
Well, you have
Hi Duncan,
thank you very much for your detailed description. For this reason, i
will wait now and hope that everything will end well.
best regards,
Franziska
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
On Wed, Jun 25, 2014 at 06:55:49PM -0500, Eric Sandeen wrote:
open_ctree() is almost 1000 lines long. I've started trying
to refactor it, primarily into helper functions, and also
simplifying (?) things a bit at the beginning by removing the
ret = func(); if (ret) { err = ret; goto ... }
On Wed, Jun 25, 2014 at 12:00:44AM +0900, Sergey Senozhatsky wrote:
Add compression `workspace' in free_workspace() to
`idle_workspace' list head, instead of tail. So we have
better chances to reuse most recently used `workspace'.
Signed-off-by: Sergey Senozhatsky
On 6/25/14, Duncan 1i5t5.dun...@cox.net wrote:
Imran Geriskovan posted on Wed, 25 Jun 2014 15:01:49 +0200 as excerpted:
Note that gdisk gives default 8 sector alignment value for AF disks.
That is 'sector' meant by gdisk is 'Logical Sector'!
Sufficiently determined user may create misaligned
On Jun 25, 2014, at 7:01 AM, Imran Geriskovan imran.gerisko...@gmail.com
wrote:
On 6/23/14, Martin K. Petersen martin.peter...@oracle.com wrote:
Anyway. The short answer is that Linux will pretty much always do I/O in
multiples of the system page size regardless of the logical block size
of
The chattr(1) manpage suffers from the same problems mount(1)
had: many options listed, not kept up to date for various
filesystems.
I've submitted a manpage update for chattr(1) which says to
refer to filesystem-specific manpages for supported attributes;
this patch updates btrfs(5) to list the
On 6/25/14, Chris Murphy li...@colorremedies.com wrote:
On Jun 25, 2014, at 1:47 AM, Hugo Mills h...@carfax.org.uk wrote:
The question is, why? If you have enough disk media errors to make
it worth using multiple copies, then your storage device is basically
broken and needs replacing, and
Hi Franziska,
(2014/06/26 20:34), Franziska Näpelt wrote:
Hi Satoru,
I'm sorry, but the boot process is always runnig(i hope so), i can't
login until now. So therefore i have currently no logs.
I don't want to interrupt these process, because there are a lot of
fileactions on the harddrive
On Thu, 26 Jun 2014 13:25:09 Duncan wrote:
properly. And if you do automated snapshots, use a good thinning script
to thin them down so you're well under 500. (I've posted figures where
even starting with per-minute snapshots, thinning down to 10 minute, then
to half hour within the day,
I've been getting blocked tasks on 3.15.1 generally at times when the
filesystem is somewhat busy (such as doing a backup via scp/clonezilla
writing to the disk).
A week ago I had enabled snapper for a day which resulted in a daily
cleanup of about 8 snapshots at once, which might have
Btrfs-progs will read the superblock without checking the checksum.
When all superblocks are corrupted, continuing will cause disaster.
So this patch will add checksum check for btrfs-progs when reading
superblocks.
Signed-off-by: Qu Wenruo quwen...@cn.fujitsu.com
---
disk-io.c | 15
Current btrfs will only use the first superblock, making the backup
superblocks only useful for 'btrfs rescue super' command.
The old problem is that if we use backup superblocks when the first
superblock is not valid, we will be able to mount a none btrfs
filesystem, which used to contains btrfs
Hi!
After about 12 hours of booting, the system runs now :)
The fifth harddrive is still in the btrfs-pool.
Here is the log from the crash, while the btrfs delete job runs:
Jun 25 20:34:59 hsad-srv-03 kernel: [614028.957248] [ cut
here ]
Jun 25 20:34:59 hsad-srv-03
Russell Coker posted on Fri, 27 Jun 2014 10:49:40 +1000 as excerpted:
On Thu, 26 Jun 2014 13:25:09 Duncan wrote:
properly. And if you do automated snapshots, use a good thinning
script to thin them down so you're well under 500. (I've posted figures
where even starting with per-minute
Hi Franziska,
(2014/06/27 14:00), Franziska Näpelt wrote:
Hi!
After about 12 hours of booting, the system runs now
Congratulations!
The fifth harddrive is still in the btrfs-pool.
Here is the log from the crash, while the btrfs delete job runs:
Jun 25 20:34:59 hsad-srv-03 kernel:
20 matches
Mail list logo
