From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mickael Marchand Subject: reiser4: mv changes mtime ? Date: Thu, 07 Apr 2005 10:36:26 +0200 Message-ID: <4254F10A.7060103@ujf-grenoble.fr> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com List-Id: Content-Type: text/plain; charset="us-ascii" To: reiserfs-list@namesys.com Hi, I am giving a shot at reiser4 to make rsync snapshots backups (using hard links and incremental rsync). this works definitely great apart from 2 minor bugs :) 1 : it seems that mv directory/ directory2/ changes the mtime of the directory. This is not the case with reiser3. Is this intentional ? (it basically breaks my recover-from-snapshots script which uses the mtime ;) 2 : this was posted on lkml today but it fits better here I guess : 2.6.12-rc1-mm4 config at http://www-fourier.ujf-grenoble.fr/~mmarcha/config-2.6.12-rc1-mm4.gz running on a bi-opteron (debian-amd64), I got some "flushing like mad" warning messages from reiser4 (which are safe apparently). and this soft lookup BUG caused by reiser4 I think : BUG: soft lockup detected on CPU#0! Modules linked in: ipv6 parport_pc parport eth1394 ehci_hcd uhci_hcd ohci1394 ieee1394 ohci_hcd usbcore snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd snd_page_alloc i2c_amd756 i2c_amd8111 i2c_isa w83781d i2c_sensor i2c_core e1000 Pid: 25291, comm: pdflush Not tainted 2.6.12-rc1-mm4 RIP: 0010:[] {protect_extent_nodes+382} RSP: 0018:ffff81007df45678 EFLAGS: 00000202 RAX: ffff810015c7c5e0 RBX: ffff81007c609000 RCX: ffff81001074ba60 RDX: ffff81001074b220 RSI: ffff81001074b1c0 RDI: ffff81001074b210 RBP: 0000002000000000 R08: ffff81007df458a0 R09: ffff810044068e14 R10: 000000000000001c R11: ffffffff802119a0 R12: 00007fe07df455e0 R13: ffff81007c609004 R14: ffff81007df4565c R15: 00007fe000000001 FS: 00002aaaaadfeae0(0000) GS:ffffffff806e7840(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 00002aaaaaac2000 CR3: 000000009bc83000 CR4: 00000000000006e0 Call Trace:{protect_extent_nodes+378} {extent_size+30} {txnh_get_atom+41} {alloc_extent+562} {plugin_by_unsafe_id+28} {item_length_by_coord+17} {handle_pos_on_twig+351} {flush_current_atom+2022} {flush_some_atom+458} {generic_sync_sb_inodes+723} {keventd_create_kthread+0} {reiser4_sync_inodes+229} {writeback_inodes+137} {background_writeout+124} {pdflush+0} {pdflush+316} {background_writeout+0} {kthread+217} {schedule_tail+64} {child_rip+8} {keventd_create_kthread+0} {kthread+0} {child_rip+0} Please CC-me in answers, I am not subscribed here. Cheers, Mik -- Mickael Marchand, Ingenieur de recherche CNRS Service Informatique, Institut Fourier - UFR Maths Tel : 0476635655 Fax : 0476514478