Re: maybe OT
On Fri, Mar 18, 2022 at 4:47 PM Paolo Galtieri wrote: > > I'm having issues with a VM. > > The VM was originally created under VMware and has worked fine for a > while. Today when I booted it up instead of seeing the usual MATE login > screen I get a login prompt: > > f34-01-vm: > > no matter what I enter, root or pgaltieri as login it never asks for > password and immediately says login incorrect. While it's booting I see > several [FAILED]... messages, e.g. [FAILED] to start CUPS Scheduler > > I booted the system again and this time it dropped into emergency mode. > In emergency mode I see the following messages in dmesg: > > BTRFS info (device sda2): flagging fs with big metadata feature > BTRFS info (device sda2): disk space caching is enabled > BTRFS info (device sda2): has skinny extents > BTRFS info (device sda2): start tree-log replay > BTRFS info (device sda2): parent transid verify failed on 61849600 > wanted 145639 fount 145637 > BTRFS info (device sda2): parent transid verify failed on 61849600 > wanted 145639 fount 145637 > BTRFS: error (device sda2) in btrfs_replay_log:2423 errno=-5 IO failure > (Failed to recover log tree) > BTRFS error (device sda2) open_ctree failed That's not good. The tree-log is used during fsync as an optimization to avoid having to do full file system metadata updates. Since the tree-log exists, we know this file system was undergoing some fsync write operations which were then interrupted. Either the VM or host crashed, or one of them was forced to shutdown, or there's a bug that otherwise prevented the guest operations from completing. Further, the parent transid verification failure messages indicate some out of order writes, as if the virtual drive+controller+cache is occasionally ignoring flush/FUA requests. I regularly use qemu-kvm VM with cache mode "unsafe". The VM can crash all day long and at most I lose ~30s of the most recent writes, depending on the fsync policy of the application doing the writes. But the file system mounts normally otherwise following the crash. However if the host crashes while the guest is writing, that file system can be irreparably damaged. This is expected. So you might want to check the cache policy being used, make sure that the guest VM is really shutting down properly before rebooting/shutting down the host. > > I ran btrfs check in emergency mode and it came up with a lot of errors. > > How do i recover the partition(s) so I can boot the system, or at least > mount them? I'd start with mount -o ro,nologreplay,rescue=usebackuproot Followed by mount -o ro,nologreplay,rescue=all The second one is a bit of a heavy hammer but it's safe insofar as it's mounting the fs read only and making no changes. It is also disabling csum checking so any corrupt files still get copied out, and without any corruption warnings. You can check man 5 btrfs to read a bit more about the other options and vary the selection. This is pretty much a recovery operation, i.e. get the important data out. The repair comment for this particular set of errors: btrfs rescue zero-log btrfs check --repair --init-extent-tree btrfs check --repair I have somewhat low confidence that it can be repaired rather than make things worse. So you should start out with the earlier mount commands to get anything important out of the fs first. IF those don't work and there's important information to get out, you need to use btrfs restore. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: maybe OT
The host OS is also F34. On 3/20/22 08:14, George N. White III wrote: On Fri, 18 Mar 2022 at 19:47, Paolo Galtieri wrote: I'm having issues with a VM. It would be useful to mention the host OS. From the name, I guess your VM is running Fedora 34. The VM was originally created under VMware and has worked fine for a while. Today when I booted it up instead of seeing the usual MATE login screen I get a login prompt: f34-01-vm: no matter what I enter, root or pgaltieri as login it never asks for password and immediately says login incorrect. While it's booting I see several [FAILED]... messages, e.g. [FAILED] to start CUPS Scheduler I booted the system again and this time it dropped into emergency mode. In emergency mode I see the following messages in dmesg: BTRFS info (device sda2): flagging fs with big metadata feature BTRFS info (device sda2): disk space caching is enabled BTRFS info (device sda2): has skinny extents BTRFS info (device sda2): start tree-log replay BTRFS info (device sda2): parent transid verify failed on 61849600 wanted 145639 fount 145637 BTRFS info (device sda2): parent transid verify failed on 61849600 wanted 145639 fount 145637 BTRFS: error (device sda2) in btrfs_replay_log:2423 errno=-5 IO failure (Failed to recover log tree) BTRFS error (device sda2) open_ctree failed I ran btrfs check in emergency mode and it came up with a lot of errors. How do i recover the partition(s) so I can boot the system, or at least mount them? The underlying problem could be the physical disk that holds the VM's virtual disk file, or a corrupt btrfs. Avoid doing anything that would write to the virtual disk. Make a backup copy of the virtual disk. If the physical drive is OK, use a separate VM to mount the Fedora 34 virtual disk for repair attempts. Try: https://btrfs.wiki.kernel.org/index.php/FAQ How do I recover from a parent transid verify failed error? At one time VirtualBox had issues with btrfs. You should check for similar reports for VMWare and btrfs. -- George N. White III ___ users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-le...@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: maybe OT
On Fri, 18 Mar 2022 at 19:47, Paolo Galtieri wrote: > I'm having issues with a VM. > It would be useful to mention the host OS. From the name, I guess your VM is running Fedora 34. > > The VM was originally created under VMware and has worked fine for a > while. Today when I booted it up instead of seeing the usual MATE login > screen I get a login prompt: > > f34-01-vm: > > no matter what I enter, root or pgaltieri as login it never asks for > password and immediately says login incorrect. While it's booting I see > several [FAILED]... messages, e.g. [FAILED] to start CUPS Scheduler > > I booted the system again and this time it dropped into emergency mode. > In emergency mode I see the following messages in dmesg: > > BTRFS info (device sda2): flagging fs with big metadata feature > BTRFS info (device sda2): disk space caching is enabled > BTRFS info (device sda2): has skinny extents > BTRFS info (device sda2): start tree-log replay > BTRFS info (device sda2): parent transid verify failed on 61849600 > wanted 145639 fount 145637 > BTRFS info (device sda2): parent transid verify failed on 61849600 > wanted 145639 fount 145637 > BTRFS: error (device sda2) in btrfs_replay_log:2423 errno=-5 IO failure > (Failed to recover log tree) > BTRFS error (device sda2) open_ctree failed > > I ran btrfs check in emergency mode and it came up with a lot of errors. > > How do i recover the partition(s) so I can boot the system, or at least > mount them? > The underlying problem could be the physical disk that holds the VM's virtual disk file, or a corrupt btrfs. Avoid doing anything that would write to the virtual disk. Make a backup copy of the virtual disk. If the physical drive is OK, use a separate VM to mount the Fedora 34 virtual disk for repair attempts. Try: https://btrfs.wiki.kernel.org/index.php/FAQ How do I recover from a parent transid verify failed error? At one time VirtualBox had issues with btrfs. You should check for similar reports for VMWare and btrfs. -- George N. White III ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Maybe OT] BackupPC Aborts Backup at 8GB on F23
On 02/28/2016 07:52 PM, jd1008 wrote: Where to look? Thanks. See http://forum.videohelp.com/threads/314405-Can-t-overcome-the-8gb-barrier-on-NTFS https://sourceforge.net/p/sevenzip/discussion/45797/thread/094f42d7/ https://www.ualberta.ca/dept/chemeng/AIX-43/share/man/info/C/a_doc_lib/aixbman/baseadmn/jfs_size_under.htm Well, I see, but it's odd this would occur just when the F23 upgrade was done. The last prior backup to the upgrade was a full backup; what's failing now is an incremental. Would've thought a filesize limit would've been hit before. Thanks. -- Tim Evans |5 Chestnut Court 443-394-3864|Owings Mills, MD 21117 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: [Maybe OT] BackupPC Aborts Backup at 8GB on F23
On 02/28/2016 05:44 PM, Tim Evans wrote: I have just upgraded, to F23, a CentOS 6.7 system that has been reliably running BackupPC (http://backuppc.sourceforge.net/) to back up a Windows 7 system via SMB for several years. After the F23 upgrade, which also included an upgrade of BackupPC to version 3.3.1, backups are now always aborting at about the 8GB mark, with this in the error log: 2016-02-28 14:00:02 Started incr backup on pelican (pid=325, share=C$) 2016-02-28 14:18:37 Backup failed on pelican (tar:712 Total bytes received: 8287158228) Actual byte count varies a bit from one failed backup to the next, but stays at the 8GB mark. Not sure this if this is a BackupPC issue, or something else. Maybe filesystem-related? More (possibly complicating) info; The destination for the backups is NFS mounted on the F23 server from a ReadyNAS fileserver; local filesystems on the ReadyNAS are btrfs format. NFS mount shows: raptor:/data/win on /win type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.252.6,mountvers=3,mountport=60363,mountproto=udp,local_lock=none,addr=192.168.252.6) Where to look? Thanks. See http://forum.videohelp.com/threads/314405-Can-t-overcome-the-8gb-barrier-on-NTFS https://sourceforge.net/p/sevenzip/discussion/45797/thread/094f42d7/ https://www.ualberta.ca/dept/chemeng/AIX-43/share/man/info/C/a_doc_lib/aixbman/baseadmn/jfs_size_under.htm -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Maybe OT....but?
Allegedly, on or about 08 November 2013, Roger sent: I have need to create a small dedicated web page newsletter with a number of plain text areas that may contain 50 - 1000 words. The contributor would copy and paste plain text layed out in sentences and paragraphs with appropriate markups like i or b. Quotations where included in the text passage would be delimited by i. For what it's worth, since you mention appropriate mark-up, then i is not an appropriate mark-up for a quote. If you actually use correct mark-up (i is merely for italics, b for bold, em for emphasised, q for quotes, or simply using normal quote characters, et cetera), then you stand a better chance of getting correct parsing of data. It sounds like you just want a search engine. Whether you want/need to find a ready-made one that works for your case, or you need to make your own specialised one up, isn't entirely clear from your posting. If you want to make your own, or customise an existing one, perhaps you should look at an existing one (e.g. htdig), to garner ideas about how to do it. I mention one, htdig, because I've used it as a general purpose search engine on our intranet, and know that you can tailor its output in various ways, just by customising the HTML templates it uses to construct its results pages. For more complex customising, you might look at its coding, and work things out from there. There's bound to be others, but since you mentioned postgres, it'd seem that you most want to learn about databases, first. Most search engines periodically update their database, it sounds like you need something different, if you want instant updating. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
