On Fri, Dec 5, 2014 at 11:27 AM, James West wrote:
> General idea would be to have a transient snapshot (optional quota support
> possibility here) on top of a base snapshot (possibly readonly). On system
> start/restart (whether clean or dirty), the transient snapshot would be
> flushed, and the
On Fri, Dec 5, 2014 at 10:28 AM, Tomasz Chmielewski wrote:
> On 2014-12-05 17:41, Chris Murphy wrote:
>
>> You're getting a read error when writing. This is expected when
>> writing 512 bytes to a 4k sector.
>>
>> What do you get for
>> parted /dev/sdb u s p
>
>
> Right - so we're getting these:
On Fri, Dec 05, 2014 at 03:28:58PM -0800, Robert White wrote:
> Ah...
>
> I've been thinking "ctime" is/was (still) "create time". It seems
> that somewhere in the last couple decades it became "change time";
> Or that I picked up that incorrect "create time" idea back in the
> UNIX Sys V R 3 days
On Fri, 5 Dec 2014 03:28:58 PM Robert White wrote:
> I've been thinking "ctime" is/was (still) "create time". It seems that
> somewhere in the last couple decades it became "change time"; Or that I
> picked up that incorrect "create time" idea back in the UNIX Sys V R 3
> days and just never ha
Ah...
I've been thinking "ctime" is/was (still) "create time". It seems that
somewhere in the last couple decades it became "change time"; Or that I
picked up that incorrect "create time" idea back in the UNIX Sys V R 3
days and just never had cause to think about it again...
Never mind. /si
James West posted on Fri, 05 Dec 2014 12:27:39 -0600 as excerpted:
> I'm sure some creative shell scripting could do something like this
> already,
Indeed...
> but I was more looking for something more bulletproof.
See below...
> General idea would be to have a transient snapshot (optional quo
So I was reading the wiki on the internal layout. The INODE description
says "st_ctime. Also updated when xattrs change."
Why isn't changing the xattrs a modification (st_mtime) event?
It just seems odd to me...
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the bo
Hi Chris,
On 12/05/2014 07:43 PM, Chris Mason wrote:
>
>
> On Fri, Dec 5, 2014 at 1:15 PM, Goffredo Baroncelli
> wrote:
>> On 12/05/2014 05:41 PM, David Sterba wrote:
>>> We're looking for good reasons to justify the existence of the
>>> helper, but this is still not enough IMHO. I can see the
On Fri, Dec 5, 2014 at 1:15 PM, Goffredo Baroncelli
wrote:
On 12/05/2014 05:41 PM, David Sterba wrote:
We're looking
for good reasons to justify the existence of the helper, but this is
still not enough IMHO. I can see the convenience to do it
automatically,
but this assumes no udev ava
On 12/05/2014 08:26 AM, Duncan wrote:
> Goffredo Baroncelli posted on Thu, 04 Dec 2014 19:39:37 +0100 as
> excerpted:
>
>> To check if a device is a LVM snapshot, it is checked the 'udev'
>> device property 'DM_UDEV_LOW_PRIORITY_FLAG' . If it is set to 1,
>> the device has to be skipped.
>>
>> As
This is just a random idea that popped through my mind while I was
looking into hardening a filesystem against damage, might be
impractical, but the idea seems promising, and well suited to a snapshot
file system.
I'm sure some creative shell scripting could do something like this
already, bu
On 12/05/2014 05:41 PM, David Sterba wrote:
> We're looking
> for good reasons to justify the existence of the helper, but this is
> still not enough IMHO. I can see the convenience to do it automatically,
> but this assumes no udev available which is probably rare these days.
I have the following
OK so from https://forums.opensuse.org/showthread.php/440209-ifconfig
I learnt that it's because /sbin, /usr/sbin etc is not on the normal
user's path on openSUSE (they are, on Kubuntu). Adding them to PATH
fixes the situation. (I wasn't even able to do ifconfig without giving
the password. No idea
David,
I'm just running default openSUSE 13.2 now (had to reinstall for other
reasons) and it's there. It's not something I added. Given that you're
also on either openSUSE or SLED/SLES, I'd expect your system to act
similarly as well. If not, it's downright curious.
I guess I'll ask around on th
On Wed, Dec 03, 2014 at 02:54:14PM -0500, Zygo Blaxell wrote:
> > Even with the tty/interactive shell detection in place? Maybe I
> > understood the reference to lvm/mdadm tools wrong. My idea is that the
> > scripts would work as now, no prompts there.
>
> How do we reliably distinguish between
>
On Thu, Dec 04, 2014 at 07:36:34PM +0530, Shriramana Sharma wrote:
> Well I don't know about you, but I'm just running an openSUSE 13.2
> system updated to Tumbleweed here, and even if I just hit "btrfs"
> enter (no sudo, no btrfs commands) on my regular (non-root) prompt, I
> am getting:
>
> $ bt
On Tue, Dec 02, 2014 at 08:41:35PM +0530, Shriramana Sharma wrote:
> That makes sense. Is there anywhere that the "official" SuSE
> recommended subvol layout is mentioned that I can refer to without
> having to start up an installer?
https://www.suse.com/documentation/sles-12/singlehtml/book_sle_a
Hello all,
I had a 6-device array I added a 4tb device to last night and ran the
command to remove a previous 4tb device that still worked fine
overnight. Unfortunately, one of the OTHER devices completely failed
while this was happening, and it *looks* like btrfs did the right thing
and stopped
On 2014-12-05 17:41, Chris Murphy wrote:
You're getting a read error when writing. This is expected when
writing 512 bytes to a 4k sector.
What do you get for
parted /dev/sdb u s p
Right - so we're getting these:
# parted /dev/sdb u s p
Model: ATA ST3000DM001-9YN1 (scsi)
Disk /dev/sdb: 5860
On Fri, Dec 5, 2014 at 3:03 AM, Tomasz Chmielewski wrote:
>> The first way to try to recover the current volume would be to
>> overwrite LBA 2262535088 which you should only do with the filesystem
>> unmounted. That's the sector causing the read error. If this is a 512
>> byte drive:
>>
>> dd if=/
On Fri, Dec 05, 2014 at 04:01:37PM +, Dimitri John Ledkov wrote:
> On 5 December 2014 at 15:32, Chris Mason wrote:
> > On Sun, Nov 30, 2014 at 5:57 PM, Dimitri John Ledkov
> > wrote:
> >>
> >> On 30 November 2014 at 22:31, cwillu wrote:
> >>>
> >>>
> >>> In ubuntu, the initfs runs a btrfs d
On 5 December 2014 at 15:32, Chris Mason wrote:
> On Sun, Nov 30, 2014 at 5:57 PM, Dimitri John Ledkov
> wrote:
>>
>> On 30 November 2014 at 22:31, cwillu wrote:
>>>
>>>
>>> In ubuntu, the initfs runs a btrfs dev scan, which should catch
>>> anything that would be missed there.
>>>
>>
>> I'm s
On Sun, Nov 30, 2014 at 5:57 PM, Dimitri John Ledkov
wrote:
On 30 November 2014 at 22:31, cwillu wrote:
In ubuntu, the initfs runs a btrfs dev scan, which should catch
anything that would be missed there.
I'm sorry, udev rule(s) is not sufficient in the initramfs-less case,
as outlined.
Fedora Core21 with 3.17.4-301.fc21.x86_64
Now BTRFS sux bigtime :-/
And my syslog is full of :
éc. 05 14:28:11 vajra kernel: [ cut here ]
déc. 05 14:28:11 vajra kernel: WARNING: CPU: 3 PID: 613 at fs/btrfs/delayed-
inode.c:1410 btrfs_assert_delayed_root_empty+0x39/0x40 [b
On 2014-12-05 07:19, Austin S Hemmelgarn wrote:
On 2014-12-05 02:42, Satoru Takeuchi wrote:
Hi Austin,
(2014/12/04 23:31), Austin S Hemmelgarn wrote:
I've recently noticed on some of my systems, that btrfs fi df
doesn't consistently show all of the chunk types.
I'll occasionally not see the Gl
On 2014-12-05 02:42, Satoru Takeuchi wrote:
> Hi Austin,
>
> (2014/12/04 23:31), Austin S Hemmelgarn wrote:
>> I've recently noticed on some of my systems, that btrfs fi df
>> doesn't consistently show all of the chunk types.
>> I'll occasionally not see the GlobalReserve, or even anything
>> but S
The first way to try to recover the current volume would be to
overwrite LBA 2262535088 which you should only do with the filesystem
unmounted. That's the sector causing the read error. If this is a 512
byte drive:
dd if=/dev/zero of=/dev/sdb count=1 seek=2262535088
It is a 512 byte drive.
Unf
27 matches
Mail list logo
